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

Pim: In SM mode, when there are both * G and SG routes, the join flag of the SG route out interface cannot be removed when receiving the SG prune message, only the join flag of the channel is removed #14987

Open
1 of 2 tasks
mayise opened this issue Dec 12, 2023 · 7 comments
Labels
triage Needs further investigation

Comments

@mayise
Copy link

mayise commented Dec 12, 2023


Describe the bug

  • Did you check if this is a duplicate issue?
  • Did you test it on the latest FRRouting/frr master branch?

To Reproduce

Expected behavior

Screenshots

Versions

  • OS Version:
  • Kernel:Linux version 4.19.139
  • FRR Version:8.5

Additional context

@mayise mayise added the triage Needs further investigation label Dec 12, 2023
@mayise
Copy link
Author

mayise commented Dec 12, 2023

*G and SG route have different iifs and the same oif. Received SG prune message from OIF.

@donaldsharp
Copy link
Member

Please actually provide a topology and output that shows the problem and steps to how you get it into this state. Without this minimal set of data this will be going no where.

@mayise
Copy link
Author

mayise commented Dec 18, 2023

@donaldsharp
图片
The test topology is shown in the figure above.

When the ge1 interface of the device under test receives the JOIN packet between *G and SG, the PIM running status is as follows:
图片

Then, the ge1 interface of the device under test receives a SG type prune packet, and the PIM running status is as follows:
图片

There may be errors in the handling here.

Copy link

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.

@Jafaral
Copy link
Member

Jafaral commented Jun 16, 2024

Should test this

@Jafaral Jafaral removed the autoclose label Jun 16, 2024
Copy link

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 Dec 14, 2024

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

@frrbot frrbot bot closed this as completed Dec 21, 2024
@frrbot frrbot bot closed this as completed Dec 21, 2024
@frrbot frrbot bot removed autoclose labels Dec 21, 2024
@Jafaral Jafaral reopened this Dec 23, 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

3 participants