1 # This is a POSIX shell fragment -*- sh -*-
3 # To configure the secure channel, fill in the following properly and
4 # uncomment them. Afterward, the secure channel will come up
5 # automatically at boot time. It can be started immediately with
6 # /etc/init.d/openflow-switch start
7 # Alternatively, use the ofp-switch-setup program to do everything
10 # NETDEVS: Which network devices should the OpenFlow switch include?
12 # List the network devices that should become part of the OpenFlow
13 # switch, separated by spaces. At least two devices must be selected
14 # for this machine to be a useful switch. Unselecting all network
15 # devices will disable the OpenFlow switch entirely.
17 # The network devices that you select should not be configured with IP
18 # or IPv6 addresses, even if the switch contacts the controller over
19 # one of the selected network devices. This is because a running
20 # OpenFlow switch takes over network devices at a low level: they
21 # become part of the switch and cannot be used for other purposes.
24 # IN_BAND: The OpenFlow switch must be able to contact the OpenFlow
25 # controller over the network. It can do so in one of two ways:
27 # * in-band: A single network is used for OpenFlow traffic and other
28 # data traffic; that is, the switch contacts the controller over one
29 # of the network devices selected as OpenFlow switch ports in the
30 # previous question. This is the most common case.
32 # * out-of-band: OpenFlow traffic uses a network separate from the
33 # data traffic that it controls. If this is the case, the control
34 # network must already be configured on a network device other than
35 # one of those selected as an OpenFlow switch port in the previous
38 # Set IN_BAND to yes for in-band control, or to no for out-of-band
42 # SWITCH_IP: For in-band communication with the controller, the
43 # OpenFlow switch must be able to determine its own IP address. Its
44 # IP address may be configured statically or dynamically:
46 # * For static configuration, specify the switch's IP address as a
49 # * For dynamic configuration with DHCP (the most common case),
50 # specify "dhcp". Configuration with DHCP will only work reliably
51 # if the network topology allows the switch to contact the DHCP
52 # server before it connects to the OpenFlow controller.
54 # If IN_BAND is set to "no" above, this setting has no effect.
57 # CONTROLLER: Location of controller.
58 # One of the following formats:
59 # tcp:HOST[:PORT] via TCP to PORT (default: 975) on HOST
60 # ssl:HOST[:PORT] via SSL to PORT (default: 976) on HOST
61 # The default below assumes that the controller is running locally.
62 #CONTROLLER="tcp:127.0.0.1"
64 # PRIVKEY: Name of file containing switch's private key.
65 # Required if SSL enabled.
66 #PRIVKEY=/etc/openflow-switch/of0-privkey.pem
68 # CERT: Name of file containing certificate for private key.
69 # Required if SSL enabled.
70 #CERT=/etc/openflow-switch/of0-cert.pem
72 # CACERT: Name of file containing controller CA certificate.
73 # Required if SSL enabled.
74 #CACERT=/etc/openflow-switch/cacert.pem
76 # Additional options to pass to secchan, e.g. "--fail=open"