Hi, The configuration is correct, the issue was related to the iptables firewall which by default was blocking the traffic on ens34 once assigned to VRF. On 06/11/2024 21:44, Mihai wrote:
Hi,
I am trying to run RIPv2 in VRF and this doesn't seem to work correctly. There is no RIP neighbor shown in BIRD, however a tcpdump running on the interface is showing RIP packets IN/OUT, advertising and receiving routes.
The configuration is below, am I missing something?
ipv4 table xxx; protocol direct direct_xxx { vrf "xxx"; ipv4 { table xxx; import all; }; interface "ens34"; } protocol rip rip_xxx { vrf "xxx"; ipv4 { import all; export all; table xxx; }; interface "ens34" { metric 2; version 2; address 224.0.0.9; mode multicast; }; }
bird> show rip neighbors rip_xxx: IP address Interface Metric Routes Seen
bird> sh route table xxx Table xxx: 10.100.100.0/30 unicast [direct_xxx 2024-11-06 21:00:31] * (240) dev ens34
root:# ip link show dev ens34 3: ens34: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master xxx state UP mode DEFAULT group default qlen 1000 link/ether 00:0c:29:60:5f:76 brd ff:ff:ff:ff:ff:ff
root:# ip vrf show Name Table ----------------------- xxx 200
00:0c:29:60:5f:76 > 01:00:5e:00:00:09, ethertype IPv4 (0x0800), length 86: (tos 0xc0, ttl 1, id 22904, offset 0, flags [none], proto UDP (17), length 72) 10.100.100.2.520 > 224.0.0.9.520: RIPv2, Response, length: 44, routes: 1 or less AFI IPv4, 10.100.100.0/30, tag 0x0000, metric: 1, next-hop: self
00:0c:29:21:ff:6e > 01:00:5e:00:00:09, ethertype IPv4 (0x0800), length 66: (tos 0xc0, ttl 1, id 19130, offset 0, flags [none], proto UDP (17), length 52) 10.100.100.1.520 > 224.0.0.9.520: RIPv2, Response, length: 24, routes: 1 or less AFI IPv4, 10.11.11.11/32, tag 0x0000, metric: 1, next-hop: self
Thanks!