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

    Wrong Gateways status in Dashboard

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 2 Posters 947 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.
    • SipriusPTS Offline
      SipriusPT
      last edited by

      Hello guys,

      I have a failover set in one router, where if WAN1 (WANGW) fails it goes to WAN2 (WAN_KANGURU), and it is working fine, I have already test it. After some tests I notice a strange behaviour at Gateways status.

      For example, I am using the default WAN1, and if it lost connection, it changes the gateway to WAN2, and it changes WAN1 status to unknown and WAN2 to online (http://prntscr.com/ejgkxl http://prntscr.com/ejgunc), but when WAN1 connection come back again, WAN1 remain unknown and just WAN2 changes to offline (http://prntscr.com/ejgmd8 http://prntscr.com/ejgtm6) and both status remains. After this if i went to System/routing/gateways, enter in WAN1 and save it without doing any change, the status of this gateway goes online. But all seems to be working fine in each case (DNS and FIREWALL), just the status of WAN1 is wrong when it comes back again.

      Test scenario: I was unpluggling the uplink cable and connecting it to each WAN port.

      There is a way to solves this or am I doing anything wrong here?

      Thanks!

      1xSG-4860-1U
      1xSG-3100
      2xpfSense Virtual Machines

      1 Reply Last reply Reply Quote 0
      • SipriusPTS Offline
        SipriusPT
        last edited by

        After testing this with two different WAN connections attached, when I remove WAN1, do the same, when I connect it back now seems to be working, it seems that I cannot use the same WAN to test it from what I am seeing here.

        http://prntscr.com/ejr7po

        1xSG-4860-1U
        1xSG-3100
        2xpfSense Virtual Machines

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

          @SipriusPT:

          it seems that I cannot use the same WAN to test it from what I am seeing here.

          Eeeeeh? What do you mean ???

          1 Reply Last reply Reply Quote 0
          • SipriusPTS Offline
            SipriusPT
            last edited by

            @doktornotor:

            @SipriusPT:

            it seems that I cannot use the same WAN to test it from what I am seeing here.

            Eeeeeh? What do you mean ???

            I was testing failover with the same uplink, connected to primary wan port and then disconnected there and connected to secundary wan port, and after I change it to the inicial state (just connected to primary wan port), there was no difference in gateways state, but I was having full acess to that wan port.

            Then I got another uplink to test, and this issue disappeared.

            Compared with what I saied yesterday about DNS with failover, after I shutdown the device yesterday and turn it on today, I was no longer able to use DNS in that backup wan again.

            1xSG-4860-1U
            1xSG-3100
            2xpfSense Virtual Machines

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

              Sorry, I still don't follow. What access to WAN port? Plus, as discussed elsewhere, there's nothing wrong with your DNS.

              1 Reply Last reply Reply Quote 0
              • SipriusPTS Offline
                SipriusPT
                last edited by

                @doktornotor:

                Sorry, I still don't follow. What access to WAN port? Plus, as discussed elsewhere, there's nothing wrong with your DNS.

                From full access I was trying to say that I was able to communicate through that port, with DNS, internet, … and there was no limitation resultant of the gateway state who was unknown in that time, from lan ports. Dont know if was that your question  :-\

                I have already figure out what was happening, I have already posted the solution that I have found to solve the DNS problem in the first topic where you start helping.

                1xSG-4860-1U
                1xSG-3100
                2xpfSense Virtual Machines

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