Closed melicherm closed 5 years ago
According to our Features and Kernel Support page, PIM requires Linux kernel >= 4.18. That could explain the ENOTSUP
errors. @donaldsharp might know the details better.
This week going to test the 4.19 backports kernel. Thought it could be a kernel issue, but i was not sure.
The router handles 10Gbit traffic of aprox. 700 users and up to 2000 devices, so i cannot kill the production one, but going to test / migrate to a test router soon.
BTW PIM and IGMP works like a charm... ~ 200Mbit of Multicast traffic, but the errors are annoying and representing some kind of issue.
Thank you @rwestphal ...
Yes please try a later kernel. The operation not supported
is coming from the request to the kernel to give us mroute stats so we can switch over to spt.
@polychaeta autoclose in 3 days
Hi, testing it right now.
Still getting the same errors in the log. @donaldsharp ?
ii frr 6.0.3-1 amd64 FRRouting suite of internet protocols (BGP, OSPF, IS-IS, ...) ii frr-pythontools 6.0.3-1 all FRRouting suite - Python tools
Linux iris1 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5 (2019-06-19) x86_64 GNU/Linux
Jul 9 21:23:52 iris1 pimd[3789]: Ignoring unsupported IGMP message type: 20 Jul 9 21:23:54 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:54 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:57 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:57 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:57 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:57 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:58 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:58 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:58 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 25 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24 Jul 9 21:23:59 iris1 zebra[967]: Invalid address family: 128 received from kernel route change: 24
hello, any update on this? i get the same error but with an older 3.x kernel
Hi, getting all the time (like every second) this errors in the frr.log.
Could not find any hint what is causing this behavior.
The setup is easy (1 interface uplink - public network, 1 interface downlink - private network). PIM SM and IGMP v2 on both interfaces
Kernel: 4.10.8
FRR version: frr 6.0-1 debian9+1 amd64 BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon forked from Quagga frr-doc 6.0-1 debian9+1 all BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (documentation) frr-pythontools 6.0-1 debian9+1 all BGP/OSPF/RIP/RIPng/ISIS/PIM/LDP routing daemon (Python Tools)