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

DVMRP reporting missing last subnet that should be listed in report #14

Closed
matthew-l-weber opened this issue Sep 1, 2015 · 5 comments
Closed

Comments

@matthew-l-weber
Copy link

Based on some testing where we added a list of subnets to the DVMRP report coming from host A, it was determined that mrouted on host B (A and B are connected with a L2 switch) was always missing the last subnet reported in the DVMRP report. Some of the debug output from mrouted as well as its route dump was showing that it was processing this subnet, but wasn't transmitting it within the DVMRP report nor was it processing traffic originating from this subnet.

Reverting back to the 3.9-beta3 version of mrouted resolved this issue, while version 3.9.7 was the one exhibiting this behavior. Beyond that we haven't investigation as to where along the line the bug may have been introduced.

We are running a 3.12.19 Linux kernel.

@troglobit
Copy link
Owner

Thanks for the report! Sounds like an off-by-one bug has been introduced somewhere.

Do you plan to do some further investigation into this, e.g. narrowing down the release the bug appeared in?

@matthew-l-weber
Copy link
Author

Yeah, hoping to investigate later this week.
On Sep 1, 2015 12:11 AM, "Joachim Nilsson" notifications@github.com wrote:

Thanks for the report! Sounds like an off-by-one bug has been introduced
somewhere.

Do you plan to do some further investigation into this, e.g. narrowing
down the release the bug appeared in?


Reply to this email directly or view it on GitHub
#14 (comment).

@troglobit
Copy link
Owner

Thx! 😃

@matthew-l-weber
Copy link
Author

Found the fix and submitted #15

troglobit pushed a commit that referenced this issue Sep 12, 2015
A subnet is missing in the DVMRP report sent to it's neighbor after the
initial probe occurs.  The issue was with the traversal of a double
linked list from end to start.  Once the traversing pointer reaches the
start of routing table for loop (condition) it would break and always
drop the first subnet.

Fixes issue #14.

Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
Signed-off-by: Joachim Nilsson <troglobit@gmail.com>
@troglobit
Copy link
Owner

Merged PR #15, closing. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants