You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configuration: (eth0's ip is 100.1.1.217, and must be with RP configuration.)
ip pim rp 143.143.143.143 239.0.0.0/8
interface eth0
ip igmp
ip igmp join 239.2.1.1 200.1.1.1 <- "ip igmp join 239.2.1.1" also have this issue.
ip igmp version 2 <- "igmp version" doesn't affect this issue.
ip pim
exit
Then, an unexpected mroute ouccurs:
# do show ip mroute
IP Multicast Routing Table
Flags: S - Sparse, C - Connected, P - Pruned
R - SGRpt Pruned, F - Register flag, T - SPT-bit set
Source Group Flags Proto Input Output TTL Uptime
100.1.1.217 239.2.1.1 SFT PIM eth0 pimreg 1 00:59:51
It means the IGMP report packets were wrongly regarded as data traffic, so the unexpected <S,G> entry is created.
In pim_mroute_msg(), there are packets (src is 100.1.1.217, dst is 239.2.1.1) which ip_hdr->ip_p is 0, not IGMPv2 protocol!
Please help check it, thanks!
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.
The configuration: (eth0's ip is 100.1.1.217, and must be with RP configuration.)
Then, an unexpected mroute ouccurs:
It means the IGMP report packets were wrongly regarded as data traffic, so the unexpected <S,G> entry is created.
In pim_mroute_msg(), there are packets (src is 100.1.1.217, dst is 239.2.1.1) which
ip_hdr->ip_p
is 0, not IGMPv2 protocol!Please help check it, thanks!
The text was updated successfully, but these errors were encountered: