You can implement the entire ifTable in your sub-agent, and then use the
function add_to_init_list() with the object name prefixed by "-" to
indicate to netsnmp to not register its own ifTable. You will also have
to override the scalar ifNumber which stores the number of ifTable rows
there are.
>
HI,
I agree with Juergen. You should be seeing that object snmpInASNParseErrs
is incremented when you send a negative value for msgMaxSize.
BER uses different rules for encoding lengths, integer values,
and the values of sub-IDs of an OID.
Regards,
/david t. perkins
On Mon, 4 Feb 2008, Chun Ti
Hi, J.S.
Ah... 0xffe3 will be treat as a minus integer... And by recheck ISO/
IEC 8825-1:2003 (E) (BER encoding), I find this:
8.3.2 If the contents octets of an integer value encoding consist of
more than one octet, then the bits of the first octet and bit 8 of the
second octet:
a) shall no
On 03/02/2008, Chun Tian (binghe) <[EMAIL PROTECTED]> wrote:
> It seems that Net-SNMP has a fixed msgMaxSize in SNMPv3 message, which is
> 65507. I found this value is BER-encoded to:
>
> 0x02 (type: integer), 0x03 (length: 3), 0x00, 0xff, 0xe3 (0xffe3 = 65507)
Nope.BER encoding doesn't work
v3-maxsize-3.pcap
Description: Binary data
Attach is a pcap file which recorded this communication progress.First 4 packet is a SNMPv3/authPriv/GET PDU, I use 3-bytes msgMaxSize to get sysDescr.0's value and succeed.The fifth packet is a another talk to SNMPd, the packet is just a SNMPv3 get-requ
Hi, Net-SNMP developers
It seems that Net-SNMP has a fixed msgMaxSize in SNMPv3 message, which
is 65507. I found this value is BER-encoded to:
0x02 (type: integer), 0x03 (length: 3), 0x00, 0xff, 0xe3 (0xffe3 =
65507)
What I don't know is why this value must be encoded to a 3-bytes
inte
