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

    DHCP not assogning IP address on WAN if

    Scheduled Pinned Locked Moved
    DHCP and DNS
    7
    13
    7.9k
    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.
    • GruensFroeschliG
      GruensFroeschli
      last edited by

      If you have cable-internet: did you powercycle the modem after connecting the pfSense?
      Cable modems are basically a ethernet_to_docsis bridge.
      These bridges usually have a MAC filter built in to only allow a certain number of MACs.

      We do what we must, because we can.

      Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

      1 Reply Last reply Reply Quote 0
      • S
        subfire91
        last edited by

        @GruensFroeschli:

        If you have cable-internet: did you powercycle the modem after connecting the pfSense?
        Cable modems are basically a ethernet_to_docsis bridge.
        These bridges usually have a MAC filter built in to only allow a certain number of MACs.

        if powercycle is restart then yes numerous times. i contacted my isp's network admin and asked if they have to release/clear anything from their side. he said to me that restarting the modem releases everything. i ve also tried the mac spoof option in wan intrface settings and copied my old linkys wan port mac address. none of these worked.

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG
          GruensFroeschli
          last edited by

          You can do a tcp dump from the webgui: "Diagnostics –> Packet Capture".
          Can you run such a capture when you plug the ethernet cable in?

          If that isn't conclusive:
          Can you put a hub between your modem and the pfSense and capture with another computer with wireshark to see what goes over the cable when requesting an IP?

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • P
            pablo
            last edited by

            I am having almost exactly the same problem as the OP. It's been driving me crazy. Apart from that and the install from USB everything has been smooth. It just kills me to be stuck at this. One additional symptom (in my case) is that once in a while I will get an IP address (Comcast, Docsis 3) and I might have a WAN connection for 10-15 sec before it goes down again. It's getting the DNS servers and those are correct but the IP address is in a completely different range (24.x.x.x) than what I usually get. When I swap out my pfsense machine with my old DI-604 everything is back to normally. I've been through all the the resets, MAC address changes etc.

            1 Reply Last reply Reply Quote 0
            • D
              danswartz
              last edited by

              There are other threads related to this (IMO.)  Keep in mind pfsense uses freebsd.  I have seen issues reported where freebsd dhcp clients occasionally can't get an IP from various ISP's (including comcast.)  Never saw a resolution unfortunately.

              1 Reply Last reply Reply Quote 0
              • P
                pablo
                last edited by

                Thanks for the update. I spent a few hours going through old threads here and elsewhere and I posted a follow-up because, as you wrote, there doesn't seem to be a solution. I had my mind set on using pfSense but I've spent way too much time on this already.

                1 Reply Last reply Reply Quote 0
                • C
                  cmb
                  last edited by

                  The system logs would probably help to determine why. And a packet capture of all WAN traffic.

                  1 Reply Last reply Reply Quote 0
                  • chpalmerC
                    chpalmer
                    last edited by

                    There are many - many of us getting a dhcp supplied address from our cable ISP…  I kind of wonder if you were to try a 100mbps interface if that wouldn't connect...

                    Ive seen modems freak out with gig cards once in a while...

                    Triggering snowflakes one by one..
                    Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                    1 Reply Last reply Reply Quote 0
                    • P
                      pablo
                      last edited by

                      Thanks! I'll give it a shot. I do indeed have gigabit NICs so maybe that's the problem. I also tried two different DOCSIS 3.0 modems (Motorola and Ubee). I'm also wondering if there's any chance that it could be related  to the modem giving itself a LAN IP of 192.168.100.1 and my LAN being 192.168.0.xx…

                      1 Reply Last reply Reply Quote 0
                      • E
                        EddieA
                        last edited by

                        @pablo:

                        I'm also wondering if there's any chance that it could be related  to the modem giving itself a LAN IP of 192.168.100.1 and my LAN being 192.168.0.xx…

                        Doubtful, as that describes my setup exactly.

                        Cheers.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post