Brekeke SIP Server Wiki

OpenFlow Settings

[General] section


Select a connection mode to an OpenFlow switch.  For example, if you select “Server” mode, Brekeke SIP Server behaves as a server of OpenFlow connection.

Select “Server” mode if you use an OpenFlow switch based on an Open vSwitch (OVS).


Switch (IP address:port):

Enter the IP address and port of an OpenFlow switch.

This field is used when you select “Client” mode.


Listening Port:

Enter the port that Brekeke SIP Server is listening for Openflow connection.

This field is used when you select “Server” mode.
(Example: 6633)


Network Gateway:

Enter the IP address of a gateway which is used for data traffic (service network) in the network. If the field is left blank, Brekeke SIP Server tries to detect the default gateway.


Interface Name:

Select the network interface that is used for data traffic (service network).


[Initial Commands] section

You can define initial commands which are executed when OpenFlow connection is established.
The field accepts the same command synatx which dpctl and ovs-ofctl employ.


add-flow ipv6,idle_timeout=0,actions=flood
add-flow ipv4,idle_timeout=0,actions=flood
add-flow arp,idle_timeout=0,actions=flood



[RTP relay] section ※1

Use OpenFlow to relay RTP packets:

If you set this setting to “yes“, RTP packets are exchnaged through an OpenFlow switch without the relaying through the Brekeke SIP Server.

RTP packets flow from UA1 to UA2:


Minimum Port / Maximum Port:

Set the range of UDP ports that will be assigned for relaying RTP packets at the OpenFlow Switch.


※1. The switch needs to support OpenFlow 1.0 (Layer 2,3,4).



[Block List] section

Use OpenFlow to block packets:

If you set this setting to “yes“, OpenFlow switch blocks packets sent from the IP addresses that are listed in the Brekeke SIP Server’s Block List database.

Block packets:


Blocking Period(sec):

Set the duration of the blocking flows that OpenFlow switch keeps.


Related Links
Yes No
Suggest Edit