Changes between Version 28 and Version 29 of HowTo/ConfigureOVSWithLayer3Routing


Ignore:
Timestamp:
08/28/14 09:22:47 (5 years ago)
Author:
zwang@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ConfigureOVSWithLayer3Routing

    v28 v29  
    5858}}}
    5959The `ping` should not work.
     60
    60615. Assign the IP addresses to the OVS bridges, and add routing entries.
    6162{{{
     
    7677sudo route add -net 10.10.11.0 netmask 255.255.255.0 dev OVSbr2
    7778route -n
     79}}}
     80
     81Check the flow table of each bridges.
     82{{{
     83sudo ovs-ofctl dump-flows OVSbr1
     84sudo ovs-ofctl dump-flows OVSbr2
     85}}}
     86You should see something like below for each of them:
     87{{{
     88NXST_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
    7890}}}
    7991
     
    97109According to the output [wiki:HowTo/ConfigureOVSWithLayer3Routing/outputs#ovs-ofctlshowOVSbr1 here], the port number of `eth1` is 1.
    98110
     111Now, if you check the flow table, for each of them you should see:
     112{{{
     113NXST_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
    991198. 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.
    100120Remember to set your controller to all OVS bridges you want to control: