+Native Tunneling in Open vSwitch userspace
+------------------------------------------
Open vSwitch supports tunneling in userspace. Tunneling is implemented in
platform independent way.
ovs-appctl ovs/route/show
Add tunnel route if not present in OVS route table.
ovs-appctl ovs/route/add 172.168.1.1/24 br-eth1
-3. Add integration brdge int-br and add tunnel port using standard syntax.
+3. Add integration bridge int-br and add tunnel port using standard syntax.
ovs-vsctl add-port int-br vxlan0 -- set interface vxlan0 type=vxlan options:remote_ip=172.168.1.2
4. Assign IP address to int-br, So final topology looks like:
-
- 192.168.1.1/24
- +--------------+
- | int-br | 192.168.1.2/24
- +--------------+ +--------------+
- | vxlan0 | | vxlan0 |
- +--------------+ +--------------+
- | |
- | |
- | |
- 172.168.1.1/24 |
- +--------------+ |
- | br-eth1 | 172.168.1.2/24
- +--------------+ +---------------+
- | eth1 |----------------------------------| eth1 |
- +--------------+ +----------------
-
- Host A with OVS. Remote host.
+ 192.168.1.1/24
+ +--------------+
+ | int-br | 192.168.1.2/24
+ +--------------+ +--------------+
+ | vxlan0 | | vxlan0 |
+ +--------------+ +--------------+
+ | |
+ | |
+ | |
+ 172.168.1.1/24 |
+ +--------------+ |
+ | br-eth1 | 172.168.1.2/24
+ +--------------+ +---------------+
+ | eth1 |----------------------------------| eth1 |
+ +--------------+ +---------------+
+
+ Host A with OVS. Remote host.
With this setup, ping to VXLAN target device (192.168.1.2) should work
There are following commands that shows internal tables:
ovs-appctl ovs/route/show
To del route:
ovs-appctl ovs/route/del <IP address>/<prefix length>
+ To look up and display the route for a destination:
+ ovs-appctl ovs/route/lookup <IP address>
ARP:
To see arp cache content: