While applying a patch to support detecting gigabit interfaces on linux, I
noticed a bug in the ifSpeed implementation. The ifSpeed object description
states:
An estimate of the interface's current bandwidth in bits
per second.
So, it seems to me that an interface that is not running or is down, the
estimate for the current bandwidth would be 0. It is currently reported as the
minimum supported speed of the interface (eg a down gigabit interface will
report 10 mbit).
The fix is very easy, but it is a definite change in behaviour. I see it as
in-line with the MIB description (and it's how my gigabit switch works).
Objections to classifying as a bug fix, and putting in 5.1.3 and above?
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders