-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
snmpbulkwalk stopped working #15680
Comments
@MattiKoskinenUnikie Have you tried to revert commit 438ef98 to see if it fixes the issue? |
I tried, and it fixed. |
louis-6wind
added a commit
to louis-6wind/frr
that referenced
this issue
Apr 23, 2024
This reverts commit 438ef98. The previous code was correct even if the coverity scanner was complaining. Fixes: FRRouting#15680 Signed-off-by: Louis Scalbert <louis.scalbert@6wind.com>
louis-6wind
added a commit
to louis-6wind/frr
that referenced
this issue
Apr 23, 2024
This reverts commit d9bd9eb. The previous code was correct even if the coverity scanner was complaining. Fixes: FRRouting#15680 Signed-off-by: Louis Scalbert <louis.scalbert@6wind.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
after updating version of FRRouting from 8.4 to 9.1we started getting errors when executing snmpbulkwalk … .1.3.6.1.2.1.14
STDERR:
Error: OID not increasing: OSPF-MIB::ospfIfIpAddress.172.0.100.1.0
I suspect that this is due to commit 438ef98
The offset is advanced by one even though IN_ADDR_SIZE number of items are read.
The text was updated successfully, but these errors were encountered: