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

    Multi-WAN, both lines down after power test, lines do not reconnect/connection

    2.0-RC Snapshot Feedback and Problems - RETIRED
    4
    14
    4.7k
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      You have your DNS servers set to 8.8.8.8 and 8.8.4.4 and one on each gateway?

      Steve

      1 Reply Last reply Reply Quote 0
      • N
        Nachtfalke
        last edited by

        @stephenw10:

        You have your DNS servers set to 8.8.8.8 and 8.8.4.4 and one on each gateway?

        Steve

        Yes, but I have got another one for each WAN. Take a look at my screenshot.

        BUT I have got the monitor IPs on 8.8.8.8 and 8.8.4.4
        Both are google DNS servers….could it possible that both went down !?
        But they were working later but pfsense wasn't able to work as it did before.

        ---- edit ----
        Another thing which is curious is in the RRD graphs. Why is there "GW_WAN" displayed ?
        I do not have such a gateway as you can see in my first post.
        Not sure if this all has something to do with my problem posted in the first post.

        DNS.jpg
        DNS.jpg_thumb

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          I tested a little bit with my pfsense.

          In general, if both WAN1 and WAN2 are UP, then the default GW is WAN1 ( 192.168.1.1 ). Then pfsense is able to check for updates. For testing purposes I restartet my router for WAN1 and the routing table in pfsense changed. The default GW is now my LAN address ( 172.16.0.254 ). Of course this is not correct and because of this pfsense cannot check for updates.

          ![WAN1 down.jpg](/public/imported_attachments/1/WAN1 down.jpg)
          ![WAN1 down.jpg_thumb](/public/imported_attachments/1/WAN1 down.jpg_thumb)
          ![Default_GW_WAN down.jpg](/public/imported_attachments/1/Default_GW_WAN down.jpg)
          ![Default_GW_WAN down.jpg_thumb](/public/imported_attachments/1/Default_GW_WAN down.jpg_thumb)

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

            Hmm,
            Why do you have LAN set as a gateway? That must cause problems.

            I have that same issue with my RRD graphs. It still maintains graphs for any gateways that have ever existed. I renamed one at one time so now it has an empty graph.

            Steve

            Edit: See this post.

            1 Reply Last reply Reply Quote 0
            • N
              Nachtfalke
              last edited by

              @stephenw10:

              Hmm,
              Why do you have LAN set as a gateway? That must cause problems.

              Because I am using another pfsense in routing mode behind my first one and so I have to create a static route with gateway.

              I have that same issue with my RRD graphs. It still maintains graphs for any gateways that have ever existed. I renamed one at one time so now it has an empty graph.

              Steve

              Thanks for info. So that shouldn't be cause of my problem. :-(

              1 Reply Last reply Reply Quote 0
              • E
                eri--
                last edited by

                Uncheck the advanced option of switching gateways.

                1 Reply Last reply Reply Quote 0
                • N
                  Nachtfalke
                  last edited by

                  @ermal:

                  Uncheck the advanced option of switching gateways.

                  I did this yesterday and it kicked me off my OpenVPN and this morning there wasnt any connection to the internet possible.

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

                    Looks like a fix?
                    https://github.com/bsdperimeter/pfsense/commit/e56a730636d36714b29fdec9947f4b8d0f2ff443

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • N
                      Nachtfalke
                      last edited by

                      @stephenw10:

                      Looks like a fix?
                      https://github.com/bsdperimeter/pfsense/commit/e56a730636d36714b29fdec9947f4b8d0f2ff443

                      Steve

                      I read this. I will test a new snap tomottow when I am on work and can get close to my server ;)

                      PS: Why cant pfsense get any updates when in MultiWAN with WAN1 (default GW) and WAN2 and WAN1 is down ? Then the GUI is slower and it ends in "unable to check for updates"
                      For me it feels like Multi-WAN is a little bit "buggy" when it does failover. But perhaps this is only my feeling.

                      Nevertheless thank you very much for taking time and giving advice.

                      1 Reply Last reply Reply Quote 0
                      • M
                        Metu69salemi
                        last edited by

                        Is there possibility to that pfsense itself can't use failover dns

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post