> if you look at packet #15 in the 'good' snoop trace, you can see > that what appears on the wire is ".1.3.6.1.4.1.9.5.1.4.1.1.6.1.1" > (portOperStatus.1.1), i.e. the OID which this script wants. > > yet, if you look at packet #15 in the 'bad' snoop trace, you can > see that what appears on the wire is "0.1" (ccitt.1)
Actually, looking at the packet dump, the OID that's being requested in the 'bad' trace is actually "1" (i.e. "iso"), but I suspect this may be a red herring. Because the following request appears to be asking for "2". What I suspect is happening is that the 'bad' requests are just taking the last subidentifier from the intended OID - i.e. the second instance value. It is possible to tweak the script to request a (deliberately bogus) OID, such as ".1.3.6.1.4.1.9.5.1.4.1.1.6.1.99" If I'm right, then the 'bad' trace will attempt to ask for ".99" (which isn't actually a valid OID, so building the packet may well fail anyway) Dave ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Net-snmp-users mailing list [EMAIL PROTECTED] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
