Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Snmp query returns 48.0.0.0 as the interface

    SNMP
    1
    2
    1.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      snm777
      last edited by

      We are attempting to figure out why when we run the Zenos SNMP interface modeler against a pfsense firewall running 2.2.4, it errors out.  We have one fw running 2.2.4 that works, and 5 others that don't.  The difference seems to be what is returned for the interface when we walk it like so:

      snmpwalk -v2c -c <key><host>IP-MIB::ipAdEntNetMask

      the interface IP that is returned is 0.0.0.0 on both the one that works and the one that doesn't, but the mask is 48.0.0.0 on the broken one and the 0.0.0.0 on the one that works.

      All of these pfsense boxe are virtual.  THe "working" one has open-tools 1280544.11 - one of the non working ones has 1280544.12, and the others don't have the tools installed at all yet.

      I am concerned that this is a known bug or regression in bsnmpd, per this entry I found in redmine:
      https://redmine.pfsense.org/issues/4298

      It appears this was entered in January of this year by someone but hasn't been taken up.  I've seen a few other posts in the forums that might be related, but no one else that I've found has posted about the 48.0.0.0 mask.

      Can anyone ehlp with this? I'm willing to do more torubleshooting, but I'm kind of stuck where to go.  a ifconfig does not show this interface at the FreeBSD level - there is nothing in config.xml referencing an interface with an ip fo 48.0.0.0.  I'm out of ideas at the moment.</host></key>

      1 Reply Last reply Reply Quote 0
      • S
        snm777
        last edited by

        I had to open a case on this with pfsense - they were able to replicate the problem not only in pfsense, but FreedBSD 10.2, which indicates that this is a bug in bsnmpd that needs to go to the attention of the FreeBSD project.  I've submitted a problem report to FreeBSD here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203264 - hopefully I formatted ti well enough that it won't rate an immediate close :)

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.