[retronet] OvS cloud progress…

[Grant Taylor]

TL;DR:  I have a (mock) RetroNet client pinging

I have a functional WireGuard VPN between a local network namespace 
(using Linux native VTEP) and rn-conc-01.

I have configured OvS on rn-conc-01 and rn-services-01 to pass VXLAN 
traffic from my local NetNS (through the WireGuard VPN), through OvS on 
rn-conc-01, to an OvS VTEP on rn-services-01.

I have 100.127.255.250/30 bound to my local VTEP and 100.127.255.249/30 
bound to the VTEP rn-services-01.

I configured the following OpenFlow rules on rn-conc-01:

  · in_port=1,tun_id=3,actions=output:2   # port 1 faces my NetNS.
  · in_port=2,tun_id=3,actions=output:1   # port 2 faces rn-services-01.

I configured the following OpenFlow rules on rn-services-01:

  · in_port=1,tun_id=3,actions=output:2   # port 1 faces rn-conc-01
  · in_port=2,actions=set_field:3->tun_id,output:1   # port 2 is the VTEP.

OvS VTEPs use a tunnel ID of 0.  So I have to change it to something 
useful as traffic comes into OvS from the Linux kernel.



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mailman.chivanet.org/pipermail/retronet/attachments/20180916/aab1b1ed/attachment.bin>