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

    Upgraded to pfSense 2.6 now I get "Interface stopped distributing possible flapping"

    Scheduled Pinned Locked Moved L2/Switching/VLANs
    3 Posts 1 Posters 724 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.
    • neogridN
      neogrid
      last edited by

      So I updated pfSense from 2.5.2 to 2.6 via the GUI, that seemed to go ok, then I noticed that all the gateways were down.

      Inspecting the console I noticed that I was getting an error message stating igb2, igb3, igb4.,igb5 Interface stopped distributing possible flapping. These 4 interfaces are all in a LACP lagg from my pfSense box to my switch. This error doesn’t come up in 2.5.2.

      Tried doing a clean install of 2.6 and restoring the config but the same error pops up.

      Presumably it has something to do with the LACP/LAGG but that has been working without any issues for several versions of pfSense. Not totally sure how to resolve this. I could do a manual rebuild but that will take a considerable amount of time … Any ideas ??

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • neogridN
        neogrid
        last edited by

        For anyone interested, I think I have stumbled upon a possible solution outlined here my switch has a choice of an LACP or Static LAGG, so I’m assuming that the Netgear LACP is not the same as the FreeBSD active mode LACP.

        I won’t be able to test out the solution until the weekend, in the event someone else has the same problem and applies the solution it would be handy to know the result.

        1 Reply Last reply Reply Quote 0
        • neogridN
          neogrid
          last edited by

          After testing out the entry in the tunables it didn't make any difference.

          net.link.lagg.0.lacp.lacp_strict_mode

          My lagg was on 0 so that entry ought to be correct.

          Any ideas how to address this ?

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