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

    2WIRE modem not giving out IP to PFSense

    Scheduled Pinned Locked Moved DHCP and DNS
    6 Posts 3 Posters 1.1k 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.
    • A
      awesomes8wc3
      last edited by

      I have this 2WIRE 2071-A modem that I use for my internet, it works great. I plug it into something, it gets an IP and it can get on the network. Except for my PFSense router.

      No matter if i put it in bridge mode, change NICs, make the IP static, change cables, reboot, reboot, reboot, it just won't connect. If I use DHCP, in PFSense the WAN box is either blank or 0.0.0.0. If I reboot it hangs on startup.

      Heres the thing though, if I plug it into a switch it gets an IP fine and I can access the internet as normal.

      Kind of a pain because I don't really have any spare switches…

      I have a shitty old Netcomm NB5 which works, but because of the TI backdoors and the buggy firmware (user+pass "isp" lets you in), the connection sucks (constant dropouts) and you can't access the internal network from the outside (it sends you to the modem admin page, which has been a known bug and was going to be "fixed" since 2005), I don't want to use it.

      I'm fairly new to PFSense so i'm probably missing something. :P

      Help appreciated.

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

        Did you make sure you were using a cross-over cable between your pfSense box and your modem?

        1 Reply Last reply Reply Quote 0
        • A
          awesomes8wc3
          last edited by

          Sorry for not replying, I thought I would get an email if I got a reply, but I didn't. Lucky I checked back here.

          The cable does say "cross over", so I trust it.

          If I boot into Windows or something it gets an IP and it works, just not in pf.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            If you put a switch between the WAN port and the modem and it works, are you using the same crossover cable?  Sure sounds like a cabling issue.  What does Status->Interfaces say for WAN when you have the modem connected but not getting an IP?

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • A
              awesomes8wc3
              last edited by

              @Derelict:

              If you put a switch between the WAN port and the modem and it works, are you using the same crossover cable?  Sure sounds like a cabling issue.  What does Status->Interfaces say for WAN when you have the modem connected but not getting an IP?


              As I said before, only this modem does it. I tried another one and it works fine.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                If it were me I'd put a blank VLAN on a managed switch between the two, and capture the traffic during DHCP and see what's going on.

                You could run a packet capture on pfSense but I would rather have a mirror/monitor port doing it so you're positive you're not experiencing something on the wire that just isn't being picked up by the NIC and sent to tcpdump.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

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