Two days ago I upgraded OpenWrt from version 24.10.2 to 24.10.3. Since then I have a problem with frr’s ripd. My router uses a source port of 613 that seems not to be accepted by the frr ripd at the other side. No routes are learned. This situation has worked for a few weeks without problems on 24.10.2.
This is what I’m seeing doing a tracedump (10.48.77.10 is my interface):
root@OpenWrt02:~# tcpdump -ni kerkbuurt port 520
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on kerkbuurt, link-type RAW (Raw IP), snapshot length 262144 bytes
10:08:48.633648 IP 10.48.77.10.613 > 10.48.77.9.520: RIPv2, Response, length: 44
10:08:49.535762 IP 10.48.77.10.520 > 10.48.77.11.520: RIPv2, Request, length: 24
10:08:49.544185 IP 10.48.77.9.520 > 10.48.77.10.520: RIPv2, Response, length: 264
10:08:53.068222 IP 10.48.77.9.520 > 10.48.77.10.520: RIPv2, Response, length: 264
10:08:53.634119 IP 10.48.77.10.613 > 10.48.77.9.520: RIPv2, Response, length: 44
10:08:58.068231 IP 10.48.77.9.520 > 10.48.77.10.520: RIPv2, Response, length: 264
10:08:58.634278 IP 10.48.77.10.613 > 10.48.77.9.520: RIPv2, Response, length: 44
^C
7 packets captured
7 packets received by filter
0 packets dropped by kernel
In vtysh the command sh ip rip status gives the following result:
OpenWrt02# sh ip rip status
Routing Protocol is "rip"
Sending updates every 5 seconds with +/-50%, next due in 2 seconds
Timeout after 15 seconds, garbage collect after 20 seconds
Outgoing update filter list for all interface is not set
Incoming update filter list for all interface is not set
Default redistribution metric is 1
Redistributing:
Default version control: send version 2, receive version 2
Interface Send Recv Key-chain
br-lan 2 2
eth3 2 2
kerkbuurt 2 2
Routing for Networks:
10.48.77.8/30
10.109.0.0/24
10.109.100.0/24
10.48.77.9
Routing Information Sources:
Gateway BadPackets BadRoutes Distance Last Update
10.48.77.9 9444 0 120 00:00:04
Distance: (default is 120)
The BadPackets counter goes up every few seconds.
The situation is as follows:
My side is a x86 VM in Proxmox running OpenWrt. I’ve configured frr ripd to advertise the networks 10.109.0.0/24 and 10.109.100.0/24 and 10.48.77.8/30.
Between my router and the router on the other side (running Vyos and also frr ripd) is a vpn created by Wireguard. We want to advertise a few subnets on each side of the vpn.
On the Vyos router there hasn’t been a configuration change on ripv2 for weeks now.
The vpn has on my side a inside interface of 10.48.77.10 and at the other side the inside interface has address 10.48.77.9. Those addresses are used as neighbour IP’s for ripv2.
My frr configuration is as follows:
OpenWrt02# sh run
Building configuration...
Current configuration:
!
frr version 10.2.1
frr defaults traditional
hostname OpenWrt02
log syslog
!
password zebra
!
router rip
neighbor 10.48.77.9
network 10.48.77.8/30
network 10.109.0.0/24
network 10.109.100.0/24
timers basic 5 15 20
version 2
exit
!
access-list vty seq 5 permit 127.0.0.0/8
access-list vty seq 10 deny any
!
line vty
access-class vty
exit
!
end
As said, using OpenWrt 24.10.2, everything worked without problems (same configuration). Since the update the dynamic routing is not working anymore.
Anyone else seeing this problem and maybe having a solution?
