Need help with faucet?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

faucetsdn
380 Stars 157 Forks Apache License 2.0 11.0K Commits 38 Opened issues

Description

FAUCET is an OpenFlow controller for multi table OpenFlow 1.3 switches, that implements layer 2 switching, VLANs, ACLs, and layer 3 IPv4 and IPv6 routing.

Services available

!
?

Need anything else?

Contributors list

Faucet

.. image:: https://github.com/faucetsdn/faucet/workflows/Unit%20tests/badge.svg?branch=master :target: https://github.com/faucetsdn/faucet/actions?query=workflow%3A%22Unit+tests%22

.. image:: https://github.com/faucetsdn/faucet/workflows/Integration%20tests/badge.svg?branch=master :target: https://github.com/faucetsdn/faucet/actions?query=workflow%3A%22Integration+tests%22

.. image:: https://codecov.io/gh/faucetsdn/faucet/branch/master/graph/badge.svg :target: https://codecov.io/gh/faucetsdn/faucet

FAUCET is an OpenFlow controller for multi table OpenFlow 1.3 switches, that implements layer 2 switching, VLANs, ACLs, and layer 3 IPv4 and IPv6 routing, static and via BGP. It is based on Waikato University's

Valve 
_ and the
Ryu OpenFlow Controller 
. FAUCET's design and background is described in
ACM Queue 
.

It supports:

  • OpenFlow v1.3 (multi table) switches (including optional table features), hardware and software
  • Multiple datapaths and distributed switching under a single controller
  • VLANs, mixed tagged/untagged ports
  • ACLs matching layer 2 and layer 3 fields
  • IPv4 and IPv6 routing, static and via BGP
  • Policy based forwarding to offload to external NFV applications (Eg 802.1x via hostapd, DHCP to isc DHCPD)
  • Port and flow statistics via InfluxDB/Grafana
  • Controller health and statistics via Prometheus
  • Unit and systems tests run under Travis based on mininet and OVS

Hardware and software switch support

Detailed guides for some switches are available on

readthedocs 
_.

Faucet's design principle is to be as hardware agnostic as possible and not require Table Type Patterns. This means that Faucet expects the hardware Open Flow Agent (OFA) to hide implementation details, including which tables are best for certain matches or whether there is special support for multicast - Faucet expects the OFA to leverage the right hardware transparently.

If you are a hardware vendor wanting to support FAUCET, you need to support all the matches in

faucet/faucet_pipeline.py 
_ and pass all tests.

Installation

Please see the

installation guide 
_.

Configuration

Please see the

configuration guide 
_ for documentation regarding the general configuration of faucet and the
recipe book 
_ for configuration snippets for common use cases.

Development and testing

Please see the

developer guide 
_.

Support

We run a number of mailing lists for communication between users and developers of Faucet, as well as a low traffic mailing list for announcements of new versions:

  • https://list.waikato.ac.nz/postorius/lists/faucet-announce.list.waikato.ac.nz/
  • https://list.waikato.ac.nz/postorius/lists/faucet-dev.list.waikato.ac.nz/
  • https://lists.geant.org/sympa/info/faucet-users

Faucet dev blog by Josh Bailey available at https://www.vandervecken.com/faucet.

To create a issue, use

GitHub Issues 
_.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.