Date: Tue, 17 Apr 2018 12:10:24 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 227502] Unable to add pfsense as monitored target in ntopng Message-ID: <bug-227502-7501-UVqs1NCCes@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227502-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-227502-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227502 --- Comment #3 from Eugene Grosbein <eugen@freebsd.org> --- (In reply to Florin Samareanu from comment #2) The problem is more complex. Indeed, "In SNMP some fields are encoded with = TLV (Type Length Value), where the length specifies how many bytes to read on t= he next field" - that's true. But ASN.1/DER encoding standard states that if integer value is small enought to be fit in single byte, it MUST be encoded with single byte and using 4 bytes is not allowed for such case by this standard. snmpwalk can send small or large integers and it encodes them just right us= ing noted "minimal integer" encoding: 1 or more bytes correspongingly. bsnmpd parses both of small and large TLV fileds just fine. On the other hand, ejrh/snmp library used by ntopng ALWAYS encodes integers using 4 bytes, even for small values (R=3D1 in the test above). That is sta= ndard violation that does not pass bsnmpd's strict validation, but pass relaxed validation of net-snmpd. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227502-7501-UVqs1NCCes>