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

    Gateway status shows "online" on interface with no carrier

    2.1 Snapshot Feedback and Problems - RETIRED
    3
    5
    2.0k
    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.
    • R
      rockcreektech
      last edited by

      I have two WAN ports set up in a Tier 1 <> Tier 2 failover, and although WAN1 has no carrier (nothing even plugged into the port) when I go to Status>Gateways, it shows that it is "online" with no packet loss. Both WAN1 and WAN2 are showing very similar latency; so I'm suspicious that the monitoring ping for WAN1 is going out over WAN2 and coming back successfully. I've tried creating firewall rules that would block all traffic to and from my monitoring IP for WAN1 on the WAN2 interface, but it had no effect.

      There may be a configuration problem on my part, however my multi-wan gateway setup is exactly the same as I've always used on 2.0.1 and 2.0.2.

      2.1-BETA1 (i386)
      built on Tue Mar 5 07:27:06 EST 2013

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

        Can you open a bug request on redmine.pfsense.rog about this.
        It is an issue of the monitor used, apinger.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          Last time this happened to me, I had a static route for the monitor IP that was, in fact, sending it out over the wrong gateway.

          Check your monitor IPs against the routing table and DNS servers and static routes.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

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

            Its a software issue of apinger.
            pfSense already adds the routes but whenthe interface goes down i think the routes and socket gets re-configured wrongly.

            1 Reply Last reply Reply Quote 0
            • R
              rockcreektech
              last edited by

              @jimp:

              Last time this happened to me, I had a static route for the monitor IP that was, in fact, sending it out over the wrong gateway.

              Check your monitor IPs against the routing table and DNS servers and static routes.

              I have no static routes so I don't think that's the issue.

              @ermal:

              Its a software issue of apinger.
              pfSense already adds the routes but whenthe interface goes down i think the routes and socket gets re-configured wrongly.

              I'll open a ticket as soon as I have a minute. Thanks for the replies.

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