1 .TH controller 8 "May 2008" "OpenFlow" "OpenFlow Manual"
4 controller \- simple OpenFlow controller reference implementation
8 [OPTIONS] ptcp:[\fIPORT\fR] | nl:\fIDP_IDX\fR
11 A sample OpenFlow controller which functions as an L2 MAC-learning
12 switch or hub. \fBcontroller\fR can manage a remote datapath through
13 a secure channel (see \fBsecchan(8)\fR). It can also connect directly
14 to a local datapath via netlink.
16 To connect over netlink to a local datapath number \fIDP_IDX\fR (Linux
17 only), specify nl:\fIDP_IDX\fR on the command line. To listen for
18 TCP connections from remote datapaths on port \fIPORT\fR, specify
19 ptcp:[\fIPORT\fR]. (\fIPORT\fR defaults to 975 if omitted.)
21 \fBcontroller\fR can control multiple datapaths. Multiple ptcp: or
22 nl: arguments may be given. Multiple TCP clients may connect to a
23 single TCP server port.
27 .BR \-H ", " \-\^\-hub
28 By default, the controller acts as an L2 MAC-learning switch. This
29 option changes its behavior to that of a hub that floods packets on
30 all but the incoming port.
33 .BR \-h ", " \-\^\-help
34 Prints a brief help message to the console.
37 .BR \-n ", " \-\^\-noflow
38 This is similar to the \fB\-\^\-hub\fR option, but does not add a
39 flow entry in the switch. This causes all traffic seen by the switch
40 to be passed to the controller before being sent out all but the
44 .BR \-v ", " \-\^\-verbose
45 Prints debug messages to the console.
48 .BR \-V ", " \-\^\-version
49 Prints version information to the console.
54 To connect directly to local datapath 0 over netlink (Linux only):
59 To bind locally to port 975 (the default) and wait for incoming connections from secure channels:
71 Currently \fBcontroller\fR does not support SSL.