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

    XG-7100 dpinger Not Working?

    Scheduled Pinned Locked Moved Official Netgate® Hardware
    5 Posts 2 Posters 644 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.
    • J
      jefstrongman
      last edited by

      Not really sure how to title this but this is what is happening.

      I have Charter service and about every week or two the RTT/RTTsd climbs to a point were I just unplug the modem and everything goes but down. After this last update 21.05.1 I have noticed that when I reset the modem the gateway stays down. This is running in muti wan because the charter sucks (reliability), so I have really bad (super slow) att as a back up. Anyways I have even tried to restart the dpinger (Gateway Monitoring Deamon) but still the gateway remains down. The only way I can get the gateway back up is to reboot the XG-7100.

      Does anyone have any advice on what is going on?

      J 1 Reply Last reply Reply Quote 0
      • J
        jefstrongman @jefstrongman
        last edited by

        Anyone have any ideas what could be going on?

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

          Sounds like maybe you have old states open? Potentially a bad state on the wrong WAN?

          Try clearing the state table instead of rebooting.

          Do you have gateway monitoring set the gateway IP still? That is the default but an ISP gateway does not have to respond to ping. Try setting it to something external like 8.8.8.8. Just be sure that IP is not set anywhere else to avoid a routing conflict.

          Steve

          J 1 Reply Last reply Reply Quote 1
          • J
            jefstrongman @stephenw10
            last edited by

            @stephenw10 Thank you! I had 8.8.8.8 in my DNS Server setting for WANGW and also had 8.8.8.8 as my Monitor IP for WANGW. Once I switched DNS Server setting to 1.0.0.1 WANGW came up. Didn't realize that need to be different, and that is new because it has been that way for at least a year. With a lot of modem reboots. Anyways thank you for the help!

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

              If you only have one WAN they can be the same. Or should be able to.

              The important thing to realise is that both of those settings create a static route for that IP via the gateway it's assigned to. So if you have multiple gateways and you try to use the same IP for monitoring and DNS on different gateways that creates a routing conflict.

              Steve

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