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

    Multiwan gateway goes down and never goes up again

    Scheduled Pinned Locked Moved Routing and Multi WAN
    5 Posts 2 Posters 432 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.
    • D
      dtraise
      last edited by

      Hello,

      I have al Multiwan setup with a primary Internet Provider (cabel) and a backup Internet Provider (DSL).
      The pfsense is a client in the Networks of the two routers (no Bridge mode).
      I tried here Static IPs and DHCP, to give the pfsense the Ip.
      Now here is my situation:
      I have a Gatewaygroup (IPv4) with the cabel beeing the Tier 1 and the DSL the Tier 2. Both Gateways have Monitoring active (cabel pings Cloudflare DNS, DSL pings google DNS).
      For some reason at random times the cabel Gateway goes Down, but can Ping the DNS or other Internet sites with the Ping Test.
      Then I force the DSL to be inactive the cabel goes up again.

      Has someone a Idea that I can try to get it to work?

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @dtraise
        last edited by

        We saw something similar yesterday. It looked like it saw WAN1 was up but left WAN2 as the default. If you go into the gateway groups page and, without making changes, save the group, does it start using WAN1?

        1 Reply Last reply Reply Quote 0
        • D
          dtraise
          last edited by

          Hello,
          yes after saving the Gatewaygroup and reloading the Service the WAN1 is up again.
          Do you have a fix for this?

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @dtraise
            last edited by

            No. We had some issues at this client in 2.4.4 with the fail-back not working and ended up running a cron script to load the gateway page. That didn't work in our case, a few days after upgrading. We poked and prodded for a while (over an hour) and eventually found saving that group (without any changes) changed the default gateway back.

            Given there's two of us that might imply something with 2.4.5. Since the router's at a client I can't do much troubleshooting but if you can replicate you might open a support ticket or a bug report at redmine.pfsense.org.

            1 Reply Last reply Reply Quote 0
            • S
              SteveITS Galactic Empire
              last edited by SteveITS

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