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

    Dpinger is checking an old gateway

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 221 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.
    • C
      chrcoluk
      last edited by chrcoluk

      I used to have a gateway called WAN_DHCP6. Every time a interface is cycled, a dpinger starts up checking for that gateway and of course gets errors as the gateway no longer is functioning.

      I am assuming something somewhere is broken in the configuration as in corrupted, but rather than just a basic "start again" I want to understand what is telling the dpinger to fire up and do this check so I can look to see if I can fix it manually.

      To clarify I dont mean in the GUI, there is no gateway with active checking on that name configured now, so I mean in the cli.

      --

      Fixed it.

      https://docs.netgate.com/pfsense/en/latest/config/xml-configuration-file.html

      Found 3 copies of WAN_DHCP6 from various old isps that werent showing in the GUI, removed them all as instructed by that page, also some other old ghosted WAN_DHCP and the dpinger is no longer running. I backed up before hand to be on safe side.

      pfSense CE 2.7.2

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