etingof / snmpfwd

SNMP Proxy Forwarder
http://snmplabs.com/snmpfwd/
BSD 2-Clause "Simplified" License
67 stars 18 forks source link

snmp v3 walk with ipv4 engineid based not working #46

Open moshetbl opened 4 years ago

moshetbl commented 4 years ago

Hi, I'm trying to build a proxy between V3 to V2c. Every thing is working as expected except of when the engineid if ipv4 based (valid according to rfc3411).

Thanks. client.txt server.txt

First scenario, engine id is simple numerical based as in your example, it is working. Second scenario, engine id is MAC based(rfc3411), it is working. Third scenario, engine id is text based(rfc3411), it is working. Fourth scenario, engine id is ipv4 based(rfc3411), no route.

query: snmpwalk -v3 -l authPriv -u igort -a MD5 -A 123456789 -x AES -X 012345678900 -e 0x80001DFC010A030301 10.3.3.1:161

error: 2020-02-03 09:05:33,910 receiveMessage: pduType <TagSet object at 0x9e713ac tags 128:32:1> 2020-02-03 09:05:33,911 processPdu: stateReference 824179, varBinds [(<ObjectName value object at 0xa17f28c tagSet <TagSet object at 0x9e02fec tags 0:0:6> payload [1.3.6.1.2.1]>, <Null value object at 0xa17f2ac subtypeSpec <ConstraintsIntersection object at 0x9e02f6c consts <SingleValueConstraint object at 0x9e02eec consts ''>> tagSet <TagSet object at 0x9e02e6c tags 0:0:5> encoding iso-8859-1 payload []>)] 2020-02-03 09:05:33,912 ERROR no route configured callflow-id=e0b12d3e84 snmp-engine-id=0x80001dfc010a030301 snmp-transport-domain=1.3.6.1.6.1.1.100 snmp-bind-address=10.3.3.1 snmp-bind-port=161 snmp-security-model=3 snmp-security-level=3 snmp-security-name=igort snmp-credentials-id=scg0 snmp-context-engine-id=0x80001dfc010a030301 snmp-context-name= snmp-context-id= snmp-pdu=GetNextRequestPDU#1.3.6.1.2.1:, snmp-content-id=any-content snmp-peer-address=192.168.24.59 snmp-peer-port=42571 snmp-peer-id=100 2020-02-03 09:05:33,913 receiveMessage: processPdu succeeded