I certainly will, I guess I was interested in people's opinion about
whether it was valid or not - I'm not really sure if the textual
conventions cover converting nodes in an OID to human readable format
or if that is all kind of ad-hoc - hence the correct solution might be
to change the length che
> On Mon, 15 Dec 2008 16:10:24 -0800, "brian retford"
> said:
br> I seem to have ruined my diff due to copy and paste stupidity, and by
br> diff'ing across 2 versions and only giving you a partial diff. Here's a diff
br> against 5.4.2.1:
Can you submit the patch to our patch tracking da
I seem to have ruined my diff due to copy and paste stupidity, and by
diff'ing across 2 versions and only giving you a partial diff. Here's a diff
against 5.4.2.1:
--- /home/brian/scratch/net-snmp-5.4.2.1/snmplib/mib.c2008-07-30
00:57:19.0 -0700
+++ snmplib/mib.c2008-12-15 15:30:14
Hello net-snmp coders. I'm implementing a MIB that supports zoned IPv4
addresses, and I'm having an issue with the way the addresses are
displayed in the client programs. The textual convention for zoned
addresses states that the value should be represented as 8 bytes with
the zone being the last f
