A pure OpenFlow software switch written in Erlang, designed for flexibility and rapid development of OpenFlow features.
LINC is an OpenFlow software switch written entirely in Erlang that runs as a userspace application. It implements multiple versions of the OpenFlow protocol and provides a flexible platform for developing and testing new networking features. The project addresses the need for a programmable, extensible software switch for SDN research and development.
Network researchers, SDN developers, and networking engineers who need a flexible OpenFlow switch for testing new protocols and features. It's particularly valuable for those working on software-defined networking innovations.
Developers choose LINC for its pure Erlang implementation that prioritizes flexibility and rapid development over performance optimization. Its modular architecture and support for multiple OpenFlow versions make it ideal for prototyping and testing new networking concepts.
OpenFlow Software Switch written in Erlang
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports OpenFlow Protocol 1.2, 1.3, and 1.4, enabling compatibility with a wide range of SDN controllers and experimental setups.
Architecture designed for easy extension, allowing developers to quickly add new functionality or modify existing OpenFlow features.
Includes tools like Sync and EDTS integration for hot-reloading and development without VM restarts, speeding up testing cycles.
Can run multiple logical switches simultaneously on a single instance, useful for simulating complex network topologies or multi-tenant scenarios.
Explicitly described as not the most efficient approach, with userspace Erlang implementation sacrificing raw speed for flexibility, making it unsuitable for high-throughput networks.
Requires manual installation of Erlang (R16 or newer) and OS-specific libraries like libpcap, with detailed steps for different Linux distributions, increasing initial deployment time.
Lacks full OpenFlow 1.4 compliance for flow entry eviction and vacancy events, as flow tables are not limited, which could hinder testing of advanced SDN features.