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

    dpinger problem after powerfail system startup

    Scheduled Pinned Locked Moved Plus 23.05 Development Snapshots (Retired)
    9 Posts 3 Posters 788 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.
    • T
      tedquade
      last edited by

      23.05-RC (amd64)
      built on Tue May 09 22:45:57 UTC 2023
      FreeBSD 14.0-CURRENT

      After a complete system shutdown after a power failure, on powerup, dpinger was stuck pounding away on 192.168.0.1 and not the proper default gateway. There was proper connectivity to the ISP and beyond. Gateways status showed off-line even though the system was on-line.

      Status > Services > dpinger restart corrected the errant Gateways status.

      Ted

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

        What is 192.168.0.1? Cable modem?

        T 1 Reply Last reply Reply Quote 0
        • T
          tedquade @stephenw10
          last edited by

          @stephenw10 That's my guess but no proof. Modem status is 192.168.100.1. It's a Hitron coda 4582 in bridge mode. Internal lan IP is 192.168.0.1 when used as a wireless router/cable modem.

          Ted

          R 1 Reply Last reply Reply Quote 0
          • R
            rcoleman-netgate Netgate @tedquade
            last edited by

            @tedquade Look at https://docs.netgate.com/pfsense/en/latest/interfaces/configure-ipv4.html#dhcp and the "reject leases from" header.

            Ryan
            Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
            Requesting firmware for your Netgate device? https://go.netgate.com
            Switching: Mikrotik, Netgear, Extreme
            Wireless: Aruba, Ubiquiti

            T 1 Reply Last reply Reply Quote 0
            • T
              tedquade @rcoleman-netgate
              last edited by

              @rcoleman-netgate In my case should I set that to 192.168.0.1 or ?

              Ted

              R 1 Reply Last reply Reply Quote 0
              • R
                rcoleman-netgate Netgate @tedquade
                last edited by

                @tedquade Check your DHCP logs to see what system gave you the 192.168.0.x IP and set it to that.

                Ryan
                Repeat, after me: MESH IS THE DEVIL! MESH IS THE DEVIL!
                Requesting firmware for your Netgate device? https://go.netgate.com
                Switching: Mikrotik, Netgear, Extreme
                Wireless: Aruba, Ubiquiti

                T 1 Reply Last reply Reply Quote 0
                • T
                  tedquade @rcoleman-netgate
                  last edited by

                  @rcoleman-netgate Looks like 192.168.0.1 is the culprit.
                  DHCP log is as follows:
                  May 10 14:23:00 dhclient 26539 DHCPOFFER from 192.168.0.1
                  May 10 14:23:02 dhclient 26539 DHCPACK from 192.168.0.1
                  May 10 14:23:02 dhclient 33064 ifconfig igc0 inet 192.168.0.13 netmask 255.255.255.0 broadcast 192.168.0.255
                  May 10 14:23:02 dhclient 33632 New IP Address (igc0): 192.168.0.13
                  May 10 14:23:02 dhclient 33907 New Broadcast Address (igc0): 192.168.0.255
                  May 10 14:23:02 dhclient 34176 New Routers (igc0): 192.168.0.1
                  May 10 14:23:02 dhclient 26539 bound to 192.168.0.13 -- renewal in 15 seconds.
                  May 10 14:23:17 dhclient 36373 DHCPREQUEST on igc0 to 192.168.0.1 port 67
                  May 10 14:23:17 dhclient 36373 DHCPACK from 192.168.0.1
                  May 10 14:23:17 dhclient 36373 bound to 192.168.0.13 -- renewal in 14 seconds.
                  May 10 14:23:31 dhclient 36373 DHCPREQUEST on igc0 to 192.168.0.1 port 67
                  May 10 14:23:31 dhclient 36373 DHCPACK from 192.168.0.1
                  May 10 14:23:31 dhclient 36373 bound to 192.168.0.13 -- renewal in 14 seconds.
                  May 10 14:23:45 dhclient 36373 DHCPREQUEST on igc0 to 192.168.0.1 port 67
                  May 10 14:23:45 dhclient 36373 DHCPACK from 192.168.0.1
                  May 10 14:23:45 dhclient 36373 bound to 192.168.0.13 -- renewal in 14 seconds.
                  May 10 14:23:59 dhclient 36373 DHCPREQUEST on igc0 to 192.168.0.1 port 67

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

                    Yup, reject leases from that. At least it only gives you a 30s lease though.

                    T 1 Reply Last reply Reply Quote 2
                    • T
                      tedquade @stephenw10
                      last edited by

                      @stephenw10 Done.

                      Ted

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