[Bug 242056] bsnmpd: ipv4 addresses in begemotSnmpdTransInetStatus table are reversed

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242056

            Bug ID: 242056
           Summary: bsnmpd: ipv4 addresses in begemotSnmpdTransInetStatus
                    table are reversed
           Product: Base System
           Version: 12.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: bin
          Assignee: bugs at FreeBSD.org
          Reporter: topical at gmx.net

Review D16654 replaced begemotSnmpdPortStatus with begemotSnmpdTransInetStatus
to support ipv6.

With ipv4, addresses are reversed now, i.e. they must be both specified
reversed and are shown reversed.

If you enable the following standard example line in /etc/snmpd.config

# UDP over IPv4: 127.0.0.1:161
# begemotSnmpdTransInetStatus.1.4.127.0.0.1.161.1 = 4

bsnmpd doesn't listen to 127.0.0.1. Unfortunately, you don't even get an error
messages.

But if you write the address reversed

# UDP over IPv4: 127.0.0.1:161
# begemotSnmpdTransInetStatus.1.4.1.0.0.127.161.1 = 4

bsnmp listens to 127.0.0.1 according to "netstat -an4 | grep 161"

udp4       0      0 127.0.0.1.161          *.*

Even if you query the daemon using snmpwalk, you get

BEGEMOT-SNMPD-MIB::begemotSnmpdTransInetStatus.ipv4."1.0.0.127".161.udp =
INTEGER: active(1)

So it seems that to endianess problem occurs when the daemon binds to the given
address. Probably there is some missing or superflous hton or ntoh there.

-- 
You are receiving this mail because:
You are the assignee for the bug.