Open Pengwei-Chen-1 opened 3 months ago
https://docs.frrouting.org/en/latest/overview.html#feature-matrix
Notice the minimum kernel for pim is 4.19. Please upgrade your kernel.
@donaldsharp thanks for your reply. Now our VM base on the RHEL8 which used the 4.18 kernel, and we cannot upgrade it. But from our verification, below secnario works well:
And for these errors:
it's telling you that the kernel does not support the requested feature. v6 support was implemented in the linux kernel long after the 4.19 minimum. I would hazard a guess that the v6 version of the command is just not available. As such things will not work properly. What exactly is not going to work properly.... I do not know.
hi @donaldsharp I use the RHEL 9.4(kernel 5.14) with FRR 10.0.1, the error log still exists.
[root@mcptt-cp ~]# uname -a
Linux mcptt-cp 5.14.0-427.13.1.el9_4.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Apr 10 10:29:16 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux
[root@mcptt-cp ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 9.4 (Plow)
mcptt-cp# show running-config
Building configuration...
Current configuration:
!
frr version 10.0.1
frr defaults traditional
hostname mcptt-cp
log file /var/log/frr/frr.log
log syslog informational
no ip forwarding
no ipv6 forwarding
!
interface loopback1
ipv6 pim
multicast enable
exit
!
interface traffic
ipv6 pim
exit
!
end
The error log as below:
2024/07/18 00:18:20 PIM6: [VM3TX-FD7WH] pimd/pim_ifchannel.c check_recv_upstream: RPF'(2001:72:101::94:16,ff35:94::1) not found
2024/07/18 03:31:28 ZEBRA: [WVJCK-PPMGD][EC 4043309093] netlink-cmd (NS 0) error: Operation not supported, type=RTM_GETROUTE(26), seq=510, pid=3092787401
2024/07/18 03:31:59 ZEBRA: [WVJCK-PPMGD][EC 4043309093] netlink-cmd (NS 0) error: Operation not supported, type=RTM_GETROUTE(26), seq=511, pid=3092787401
2024/07/18 03:32:30 ZEBRA: [WVJCK-PPMGD][EC 4043309093] netlink-cmd (NS 0) error: Operation not supported, type=RTM_GETROUTE(26), seq=512, pid=3092787401
Description
ipv6 pim
andospf6
IGMPv3
&MLDv2
&pim ipv6
&ospfv3
(2001:72:121::84:11,ff35:84::1)
And the problems are:
ipv6 mroute
cannot auto clear, and the error log still print out.ipv6 mroute
with commandclear ipv6 mroute
, the mroute cleared and error log will stopped.My question are:
4.18.0-544.el8.x86_64
ipv6 mroute
not cleared after multicast receiver stopped, does it related with the error log?Version
How to reproduce
Expected behavior
ipv6 mroute
should be cleared.Actual behavior
ipv6 mroute
not cleared after multicast receiver stopped.Additional context
No response
Checklist