Changes between Version 28 and Version 29 of HowTo/ConfigureOVSWithLayer3Routing
- Timestamp:
- 08/28/14 09:22:47 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HowTo/ConfigureOVSWithLayer3Routing
v28 v29 58 58 }}} 59 59 The `ping` should not work. 60 60 61 5. Assign the IP addresses to the OVS bridges, and add routing entries. 61 62 {{{ … … 76 77 sudo route add -net 10.10.11.0 netmask 255.255.255.0 dev OVSbr2 77 78 route -n 79 }}} 80 81 Check the flow table of each bridges. 82 {{{ 83 sudo ovs-ofctl dump-flows OVSbr1 84 sudo ovs-ofctl dump-flows OVSbr2 85 }}} 86 You should see something like below for each of them: 87 {{{ 88 NXST_FLOW reply (xid=0x4): 89 cookie=0x0, duration=2.135s, table=0, n_packets=0, n_bytes=0, idle_age=2, priority=0 actions=NORMAL 78 90 }}} 79 91 … … 97 109 According to the output [wiki:HowTo/ConfigureOVSWithLayer3Routing/outputs#ovs-ofctlshowOVSbr1 here], the port number of `eth1` is 1. 98 110 111 Now, if you check the flow table, for each of them you should see: 112 {{{ 113 NXST_FLOW reply (xid=0x4): 114 cookie=0x0, duration=993.757s, table=0, n_packets=0, n_bytes=0, idle_age=993, priority=0 actions=NORMAL 115 cookie=0x0, duration=61.364s, table=0, n_packets=0, n_bytes=0, idle_age=61, in_port=1 actions=LOCAL 116 cookie=0x0, duration=15.21s, table=0, n_packets=0, n_bytes=0, idle_age=15, in_port=65534 actions=output:1 117 }}} 118 99 119 8. If you want to insert these flows via your controller, you will need to either specify port 65534 explicitly or use whatever convention your controller uses to specify the `LOCAL` port of a bridge. 100 120 Remember to set your controller to all OVS bridges you want to control: