Update check_netint.pl #19
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I recently switched some of my debian systems to jessie, and check_netint.pl started not to work because all interface names where the same, with manufacturer names instead of unique interface names.
I found info here : http://serverfault.com/questions/713660/snmp-getting-the-short-interface-name-instead-of-long-ifdescr-again
It seems that the relevant info is in OID 1.3.6.1.2.1.31.1.1.1.1 instead of 1.3.6.1.2.1.2.2.1.2
Apparently there has been some confusion between ifName and ifDescr in the past : things worked before because ifDescr did, in fact, contain the name. Now debian 8 exhibits the correct behavior (see http://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.3.6.1.2.1.31.1.1.1.1 vs http://cric.grenoble.cnrs.fr/Administrateurs/Outils/MIBS/?oid=1.3.6.1.2.1.2.2.1.2)
This PR proposes to make the switch in order to recover the expected behavior. I tested it on my system.