Changes between Version 23 and Version 24 of HowTo/ConfigureOVSWithLayer3Routing


Ignore:
Timestamp:
08/27/14 17:44:13 (5 years ago)
Author:
zwang@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/ConfigureOVSWithLayer3Routing

    v23 v24  
    1616[[Image(OVS Routing detail.png, 45%, nolink)]]
    1717
    18 In summary the idea is to create a single OVS bridge for each interface on your machine that you want to assign an IP; pass the packet between the interface and the network stack through the LOCAL port of OVS; and let Linux routing handle the rest.
     18In summary the idea is to create a single OVS bridge for each interface on your machine that you want to assign an IP; pass the packet between the interface and the network stack through the `LOCAL` port of OVS; and let Linux routing handle the rest.
    1919This wiki page provides step-by-step instructions.
    2020
     
    2727}}}
    2828
    29 2. Remove the IPs of dataplane interfaces as you will assign them to the OVS bridges (your interface names may vary). On GENI, be careful not to bring down eth0, because it is your control interface, if you bring that interface down you won't be able to login to your host!
     292. Remove the IPs of dataplane interfaces as you will assign them to the OVS bridges (your interface names may vary). On GENI, be careful not to bring down `eth0`, because it is your control interface, if you bring that interface down you won't be able to login to your host!
    3030{{{
    3131sudo ifconfig eth1 0
     
    7373}}}
    7474
    75 6. When an OVS bridge is installed in the Linux OS, it is wired such that any application packets or packets routed via Linux will be sent to the LOCAL port of the OVS bridge, assuming a route to that bridge exists. And, in the reverse direction, any packets sent out an OVS bridge's LOCAL port will be received by the local networking stack.
     756. When an OVS bridge is installed in the Linux OS, it is wired such that any application packets or packets routed via Linux will be sent to the `LOCAL` port of the OVS bridge, assuming a route to that bridge exists. And, in the reverse direction, any packets sent out an OVS bridge's `LOCAL` port will be received by the local networking stack.
    7676
    7777Let's do an example of how a packet would traverse our network from 10.10.10.2 to 10.10.11.2.
     
    9292According to the output [wiki:HowTo/ConfigureOVSWithLayer3Routing/outputs#ovs-ofctlshowOVSbr1 here], the port number of `eth1` is 1.
    9393
    94 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.
     948. 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.
    9595Remember to set your controller to all OVS bridges you want to control:
    9696{{{