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

SNMP ARP Table Delay or Bug

Scheduled Pinned Locked Moved 1.2.1-RC Snapshot Feedback and Problems-RETIRED
5 Posts 2 Posters 4.5k Views
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.
  • B
    blak111
    last edited by Nov 25, 2008, 12:27 AM

    I'm not sure if this is a bug, but I have a setup that checks for arp poisoning using arpwatch. I went to test it and after I poison a host, the changed mac address to IP binding isn't reflected in the arp table retrieved from pfSense via SNMP. It does appear immediately under the ARP Tables on the web interface.
    Is this an intentional long delay to populate those SNMP arp tables, or is it just a bug of the tables not being updated with new values?

    Thanks,
    Kevin

    P.S. I verified it's not just the arpwatch program by performing an snmpwalk on the device and piping the results into grep to see the IP to MAC entry myself.

    1 Reply Last reply Reply Quote 0
    • B
      blak111
      last edited by Nov 25, 2008, 6:40 PM

      For some additional information, this only appears to be a problem on 1.2.1. The arp entries reported by a 1.2 release are updated immediately. It seems like once an entry is added to the SNMP table, it never changes.

      1 Reply Last reply Reply Quote 0
      • B
        blak111
        last edited by Nov 29, 2008, 10:39 AM Nov 29, 2008, 6:13 AM

        Do I need to post some more info or screenshots?

        1 Reply Last reply Reply Quote 0
        • Y
          YoMarK
          last edited by Dec 3, 2008, 10:12 AM

          Don't know if the SNMP agent on PfSense uses caching, but this could be the problem.

          1 Reply Last reply Reply Quote 0
          • B
            blak111
            last edited by Dec 4, 2008, 12:06 AM

            It just started happening with the 1.2.1 release, so maybe some caching did get turned on during the change. The values change right away with 1.2.

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received