Hi, I'm not interested in bridging so I tried creating the tunnels in L3 mode and perform routing between VNI 50 and VNI 70 using 2 linux namespaces :
> > create loopback interface > set interface mac address loop0 02:10:18:34:9f:cd > set interface ip address loop0 11.11.11.3/24 > set int l2 bridge loop0 1 > set int state loop0 up > > create host-interface name eth-t1 > create host-interface name eth-t2 > set interface ip address host-eth-t1 11.11.10.3/24 > > set interface state host-eth-t1 up > set interface state host-eth-t2 up > set interface mac address host-eth-t1 02:fe:ef:20:a0:ed > > create vxlan tunnel src 11.11.11.3 dst 100.0.0.2 vni 50 l3 > create vxlan tunnel src 11.11.11.3 dst 101.0.0.2 vni 70 l3 > > ip route add 100.0.0.2/32 via 11.11.11.3 loop0 > ip route add 101.0.0.2/32 via 11.11.11.3 loop0 > Sending this packet from host-eth-t1: > > Ether(dst="02:fe:ef:20:a0:ed")/IP(dst="11.11.11.3",src="100.0.0.2")/UDP(sport=1337,dport=4789)/VXLAN(vni=50,flags=8)/Ether()/IP()/UDP() > > As a first stage, I'm trying to just have the packet go through vxlan decap and perform ip4 lookup (which currently should not find a suitable route). However, after vxlan decap inner ethernet header is treated as IP header: > > 00:00:43:753410: ip4-udp-lookup > UDP: src-port 1337 dst-port 4789 > 00:00:43:753414: vxlan4-input > VXLAN decap from vxlan_tunnel0 vni 50 next 2 error 0 > 00:00:43:753417: ip4-input > unknown 238: 8.0.69.0 -> 0.28.0.1 > version 10, header length 40 > I'm probably making a simple mistake in my setup.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#20833): https://lists.fd.io/g/vpp-dev/message/20833 Mute This Topic: https://lists.fd.io/mt/88906491/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
