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

    "kernel: arp: 43:05:43:05:00:00 is multicast" spam in syslog

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 3 Posters 4.7k 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.
    • luckman212L Offline
      luckman212 LAYER 8
      last edited by

      I have a small network with pfSense running on an APU1D and an Open-Mesh WAP (OM2P-HSv2) attached to the LAN switch. In the syslog are endless "kernel: arp: 43:05:43:05:00:00 is multicast" messages every few seconds. 43:05:43:05:00:00 does not exist in my ARP table. My research[1] didn't turn up much but points to this being a side effect of something called Bridge Loop Avoidance Protocol that the openmesh folks have built in for their mesh networking (sort of like Spanning Tree but designed for lossy links)

      http://www.open-mesh.org/projects/batman-adv/wiki/Bridge-loop-avoidance-Protocol

      I didnt' see any way to disable this feature on the WAP side so I was wondering if there was a way to block these (harmless) messages from the syslog?

      1 Reply Last reply Reply Quote 0
      • D Offline
        doktornotor Banned
        last edited by

        @luckman212:

        something called Bridge Loop Avoidance Protocol that the openmesh folks have built in for their mesh networking

        Stupid… Try

        net.link.ether.inet.allow_multicast=1
        

        (see man arp(4)) – though that just breaks RFC1812 sec. 3.3.2

        1 Reply Last reply Reply Quote 0
        • luckman212L Offline
          luckman212 LAYER 8
          last edited by

          Saw that option but was scared to enable it. Seems a bad idea to violate the RFC. But I am testing it out now - so far seems to be working.  Thanks :)

          1 Reply Last reply Reply Quote 0
          • stephenw10S Offline
            stephenw10 Netgate Administrator
            last edited by

            I don't think you'll see an issue. That was the behaviour in 2.1.5 anyway but 2.2 tightened it up.
            https://redmine.pfsense.org/issues/4284

            Steve

            1 Reply Last reply Reply Quote 0
            • luckman212L Offline
              luckman212 LAYER 8
              last edited by

              Ah that makes sense.  Was running 2.1.5 on this unit until recently and never noticed the messages before. That explains it, thanks guys

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