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

    WAN going UP and DOWN in CE 2.7

    Scheduled Pinned Locked Moved Routing and Multi WAN
    ce 2.7amd64wan
    24 Posts 4 Posters 3.8k 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.
    • S
      Stef93 @Stef93
      last edited by

      @Stef93 said in WAN going UP and DOWN in CE 2.7:

      @emefff
      This seems to be something I have been struggling with for 2 weeks and finally seems to have made it. The first thing to do is System/RoutingGateways/Edit > Show Advanced Options > Packet Loss Thresholds to change the default value from 10-20 to 10-75.
      The second thing I did was remove the interface and rebind it (I had to fix it wherever nat, openvpn, etc. were indicated, a lot)
      the third thing I did was turn off the machine, completely de-energize it and make sure until the lights on the network card stopped blinking (wol) I waited another minute and only after that turned it on.
      As a result, the problem went away... https://docs.netgate.com/pfsense/en/latest/hardware/tune.html There are a lot of tips here, BUT, I suggest doing this only if there are problems! Therefore, I advise you to remove all the tuning that you could do.

      it takes a long time to explain these points, but these points were completed at intervals of 2-3 days, for example, 10-20 changed to 10-75 in order to see the losses, according to the standard> 20% losses, he considers the gateway lost

      E 1 Reply Last reply Reply Quote 0
      • E
        emefff @Stef93
        last edited by

        Hello,

        I tried the threshold change from 10-20 to 10-75 and increased the MBUFS, nothing changed.

        What did seem to get rid of the hotplugging events (at least for now 24h without any hotplugging event, which was NEVER the case since 2.7) is changing from snort to suricata. The funny thing is: sometime in CE 2.6 I changed from suricata to snort because of trouble with suricata.

        I am confident this is solved, but will report back if I was wrong,

        thanks everybody,

        Mario.

        E 1 Reply Last reply Reply Quote 0
        • E
          emefff @emefff
          last edited by

          Hi,

          I have been running this config without unplanned hotplugging events of NIC for more than a week now. It was definitely the Snort package that caused these events,

          Mario.

          1 Reply Last reply Reply Quote 0
          • J
            JPCNS
            last edited by

            Similar problem in CE2.7.2 in AGO 2024

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