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

    WAN Failed to Get DHCP IP Address (Solved)

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 5 Posters 1.2k 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.
    • NollipfSenseN
      NollipfSense
      last edited by NollipfSense

      So, yesterday I turned on my new ISP cable service and I could not get WAN to obtain DHCP IP address...could not figured that out (posting this from a friend's home)...I am baffled by this...what could it be? I keep getting 0.0.0.0! I am on pfSense 2.4, and my machine had been not used since last update in December!

      pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
      pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

      1 Reply Last reply Reply Quote 0
      • PolarmikeP
        Polarmike
        last edited by Polarmike

        Check the Ethernet cable if all's good, Disable wan and re-able it in the Interfaces settings.

        (does he get a valid IP if he plugs it directly into a computer/Laptop etc. ?)

        NollipfSenseN 1 Reply Last reply Reply Quote 0
        • NollipfSenseN
          NollipfSense @Polarmike
          last edited by

          @Polarmike said in WAN Failed to DHCP IP Address:

          Check the Ethernet cable if all's good, Disable wan and re-able it in the Interfaces settings.

          (does he get a valid IP if he plugs it directly into a computer/Laptop etc. ?)

          Yes, cable is good and yes; I get valid IP when plugged directly with a computer or my Mikrotik.

          pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
          pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            Did you power cycle the cable modem between changing devices too it?

            If you connect say pc to cable modem and get public IP, between you can connect pfsense you will almost for sure have to power cycle the cable modem... They almost always pair up with the device connected to them, when you want to change that device you need to power cycle them because the mac of the device is going to be different.

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            NollipfSenseN 1 Reply Last reply Reply Quote 1
            • NollipfSenseN
              NollipfSense @johnpoz
              last edited by

              @johnpoz said in WAN Failed to DHCP IP Address:

              Did you power cycle the cable modem between changing devices too it?

              If you connect say pc to cable modem and get public IP, between you can connect pfsense you will almost for sure have to power cycle the cable modem... They almost always pair up with the device connected to them, when you want to change that device you need to power cycle them because the mac of the device is going to be different.

              Yes, I did power cycled the cable modem...in fact, I was on the phone with the ISP as I was baffled...they saw the pfSense requests an IP, then it went to 0.0.0.0. So, I had wondered whether the IP address issued was in my block list...why the 0.0.0.0!

              pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
              pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

              JKnottJ 1 Reply Last reply Reply Quote 0
              • H
                HansSolo
                last edited by

                If you're dealing with a smaller home network, and right now you just need to get it working, you can get around this for now by assigning a Static IP (until you get it figured out)

                1 Reply Last reply Reply Quote 0
                • JKnottJ
                  JKnott @NollipfSense
                  last edited by

                  @NollipfSense said in WAN Failed to Get DHCP IP Address:

                  why the 0.0.0.0

                  That's what address devices use, until they're assigned an address. Entirely normal, though it should get an assigned address.

                  What do you mean by "then it went to 0.0.0.0"? Did that come back from the ISP? Did pfSense just use it, without accepting an offered address? This is where packet captures really come in handy, to see what's actually on the wire.

                  PfSense running on Qotom mini PC
                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                  UniFi AC-Lite access point

                  I haven't lost my mind. It's around here...somewhere...

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    @JKnott said in WAN Failed to Get DHCP IP Address:

                    This is where packet captures really come in handy, to see what's actually on the wire.

                    Exactly!!! you see pfsense send the discover - so what did they offer??

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • NollipfSenseN
                      NollipfSense
                      last edited by

                      Well, it turned out to be patience that was needed...had I wait, I would see on the dashboard that the negotiations between the cable modem and the pfSense were going on, changing WAN IP from n/a to 0.0.0.0, then, 192.168.100.10...doing that rotation a couple of times, then finally getting the proper IP address...all is good.

                      pfSense+ 23.09 Lenovo Thinkcentre M93P SFF Quadcore i7 dual Raid-ZFS 128GB-SSD 32GB-RAM PCI-Intel i350-t4 NIC, -Intel QAT 8950.
                      pfSense+ 23.09 VM-Proxmox, Dell Precision Xeon-W2155 Nvme 500GB-ZFS 128GB-RAM PCIe-Intel i350-t4, Intel QAT-8950, P-cloud.

                      1 Reply Last reply Reply Quote 0
                      • johnpozJ
                        johnpoz LAYER 8 Global Moderator
                        last edited by

                        So you cable modem wasnt actually connected to the internet yet.. ;)

                        Yeah you have to wait til its actually on the internet before it can give something behind an IP... 192.168.100.x is what it gives clients when its booted but not connected to internet.

                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                        If you get confused: Listen to the Music Play
                        Please don't Chat/PM me for help, unless mod related
                        SG-4860 24.11 | Lab VMs 2.8, 24.11

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