Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong mroute entry with IGMP report #14690

Closed
anlancs opened this issue Oct 30, 2023 · 4 comments
Closed

Wrong mroute entry with IGMP report #14690

anlancs opened this issue Oct 30, 2023 · 4 comments
Labels
triage Needs further investigation

Comments

@anlancs
Copy link
Contributor

anlancs commented Oct 30, 2023

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!

@anlancs anlancs added the triage Needs further investigation label Oct 30, 2023
@riw777
Copy link
Member

riw777 commented Oct 31, 2023

what version is this? can you make certain you're on master?

@anlancs
Copy link
Contributor Author

anlancs commented Nov 3, 2023

On stable 8.5.3.

Copy link

github-actions bot commented May 2, 2024

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.

@frrbot
Copy link

frrbot bot commented May 2, 2024

This issue will be automatically closed in the specified period unless there is further activity.

@frrbot frrbot bot closed this as completed May 9, 2024
@frrbot frrbot bot closed this as completed May 9, 2024
@frrbot frrbot bot removed the autoclose label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

2 participants