Allow adding a geneve interface to the vrf.
Description
Description
Details
Details
- Version
- VyOS 1.4.0, 1.5-rolling-202407010024
- Is it a breaking change?
- Perfectly compatible
- Issue type
- Feature (new functionality)
Related Objects
Related Objects
- Mentioned In
- rVYOSONEXc5716358c150: Merge pull request #3755 from vyos/mergify/bp/sagitta/pr-3752
rVYOSONEX3817a83f0af6: Merge pull request #3754 from vyos/mergify/bp/circinus/pr-3752
rVYOSONEX63a1639b676d: T6538: Add the ability to set GENEVE interfaces to VRF
rVYOSONEX335263ad8547: T6538: Add the ability to set GENEVE interfaces to VRF
rVYOSONEX5748db4ebb4f: T6538: Add the ability to set GENEVE interfaces to VRF
rVYOSONEXe265002fdbac: Merge pull request #3752 from sever-sever/T6538
Event Timeline
Comment Actions
There are some nuances with it, until we do not have a route from to default VRF to the peer it won't work
set vrf bind-to-all set vrf name first table '123' set interfaces ethernet eth1 address '100.64.0.1/29' set interfaces ethernet eth1 vrf 'first' set interfaces geneve gnv0 address '10.0.0.1/30' set interfaces geneve gnv0 remote '100.64.0.2' set interfaces geneve gnv0 vni '10' set interfaces geneve gnv0 vrf 'first' # After adding the PBR route to the peer (from default VRF), it starts working fine! set policy local-route rule 10 destination address '100.64.0.2' set policy local-route rule 10 set table '123'
Check
vyos@vyos# run ping 10.0.0.2 vrf first PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=4.21 ms 64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=1.01 ms 64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=0.934 ms ^C --- 10.0.0.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 0.934/2.051/4.209/1.526 ms [edit] vyos@vyos#
tcpdump on the remote site:
vyos@r2:~$ sudo tcpdump -ni gnv0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on gnv0, link-type EN10MB (Ethernet), capture size 262144 bytes 13:47:27.421170 ARP, Request who-has 10.0.0.2 tell 10.0.0.1, length 28 13:47:27.421320 ARP, Reply 10.0.0.2 is-at b2:fb:bd:48:d3:bd, length 28 13:47:27.425582 IP 10.0.0.1 > 10.0.0.2: ICMP echo request, id 3763, seq 1, length 64 13:47:27.425649 IP 10.0.0.2 > 10.0.0.1: ICMP echo reply, id 3763, seq 1, length 64 13:47:28.423218 IP 10.0.0.1 > 10.0.0.2: ICMP echo request, id 3763, seq 2, length 64 13:47:28.423357 IP 10.0.0.2 > 10.0.0.1: ICMP echo reply, id 3763, seq 2, length 64