LILiK
/
openwrt-packages-dist
5
0
Fork 0
Code Issues 0 Pull Requests 0 Projects 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
27308 Commits
1 Branch
46 MiB
Tree: de00aad596
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'de00aad596'
${ noResults }
openwrt-packages-dist/net/openvswitch/files/openvswitch.config

27 lines
600 B
Raw Normal View History

openvswitch: rework packaging New scheme mainly provides three packages: openvswitch, openvswitch-ovn-north, openvswitch-ovn-controller. These should fit most usage scenarios. Other subpackages like openvswitch-libXXX etc. are there for dependency management and are hidden from the menu. Many python and shell scripts are removed in this revision. Most of them cannot run out of box at all for lack of dependencies. Others being legacy ones are not that useful now. Add them back at later time when real need appears Below are a simple listing of additions - initscript now incorporate also ovn north and controller support - ovn-ctl and ovs-ctl can be invoked directly from within $PATH Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
7 years ago
​
openvswitch: add SSL support Open vSwitch supports SSL to connect to an OpenFlow controller. This is recommended for security. Expand the UCI ovs config section to allow configuring SSL CA, certificate and private key. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
​
​
openvswitch: rework packaging New scheme mainly provides three packages: openvswitch, openvswitch-ovn-north, openvswitch-ovn-controller. These should fit most usage scenarios. Other subpackages like openvswitch-libXXX etc. are there for dependency management and are hidden from the menu. Many python and shell scripts are removed in this revision. Most of them cannot run out of box at all for lack of dependencies. Others being legacy ones are not that useful now. Add them back at later time when real need appears Below are a simple listing of additions - initscript now incorporate also ovn north and controller support - ovn-ctl and ovs-ctl can be invoked directly from within $PATH Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
7 years ago
​
​
​
​
​
openvswitch: adds new UCI section ovs_bridge This new config section in package openvswitch supports creating a named bridge, and setting its' OpenFlow controller end-point. An example config is included in /rom/etc/config/openvswitch Signed-off-by: Simon Kinane <skinane@fb.com>
4 years ago
​
​
​
openvswitch: allow complex port configurations The current way to add ports to an Open vSwitch bridge does not allow complex port configurations. Use a dedicated uci config section per port instead of the current port:type syntax. This way we can easily support more features like setting the VLAN tag or the OpenFlow port number. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
openvswitch: add option for OpenFlow datapath desc Add a UCI config option to set the OpenFlow datapath description. This allows setting a human readable description of the bridge, e.g. "Building x, Floor y, AP z", which makes it easier to recognize the AP. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
openvswitch: support setting OpenFlow datapath ID By default, Open vSwitch will generate the OpenFlow datapath ID of a bridge based on the MAC address of one of its ports. Due to this, it's possible that the datapath ID changes when new ports are added. When the datapath ID changes, Open vSwitch disconnects from the controller, as there is no way to notify the controller that the datapath ID has changed. Add an option to set the datapath ID so that the above situation can be avoided. The option takes either exactly 16 hex characters, or when prefixed with 0x, between 1 and 16 hex characters. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
openvswitch: add option for failure mode When Open vSwitch is configured to use a controller, but is unable to connect to it, Open vSwitch will setup flows to allow all traffic, if the failure mode is not configured, or set to standalone. As this might be a security hazard, it is also possible to configure Open vSwitch in a secure failure mode. Enabling this mode causes Open vSwitch to drop all traffic if it is unable to connect to the controller. Redirect stderr of the command to /dev/null as it does not support the --if-exists option. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
openvswitch: allow complex port configurations The current way to add ports to an Open vSwitch bridge does not allow complex port configurations. Use a dedicated uci config section per port instead of the current port:type syntax. This way we can easily support more features like setting the VLAN tag or the OpenFlow port number. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
3 years ago
​
​
​
​
​
​
​
 
  1. config ovs ovs
  2. 	option disabled 1
  3. 	option ca '/etc/openvswitch/example_ca.crt'
  4. 	option cert '/etc/openvswitch/example_cert.crt'
  5. 	option key '/etc/openvswitch/example_key.crt'
  6. 

  7. config ovn_northd north
  8. 	option disabled 1
  9. 

  10. config ovn_controller controller
  11. 	option disabled 1
  12. 

  13. config ovs_bridge
  14. 	option disabled 1
  15. 	option name 'my-bridge'
  16. 	option controller 'tcp:192.168.0.1'
  17. 	option datapath_desc ''
  18. 	option datapath_id ''
  19. 	option fail_mode 'standalone'
  20. 

  21. config ovs_port
  22. 	option disabled 1
  23. 	option bridge 'my-bridge'
  24. 	option port 'ovs-port1'
  25. 	option ofport '1'
  26. 	option tag '123'
  27. 	option type 'internal'