Pfsense wont connect to WAN when directly connected to Comcast Modem (SOLVED)



  • I just setup Pfsense on an HP Proliant DL380 G4 and for some reason when I try to connect an ethernet cable directly from my Comcast modem (Ubee) to the Proliant I get a WAN adress of 0.0.0.0 and a LAN adress of 192.168.1.1. I try pinging directly from the server and I get 100% packet loss which means that the Proliant isn't connecting to the Comcast modem. However, when I connect the Comcast modem to my Apple Airport Extreme wifi router then connect my Proliant to that I will get a WAN adress of 192.168.1.4 and will be able to connect to the internet. What am I doing wrong?

    SOLVED: Unplug your modem and take its battery out. Then unplug the server and if possible remove the power supply(s). Then wait about 5-10 minutes. Put the modem battery back in and turn in on. Wait until it's up and running then replace the power supply(s) in your server and plug it back in and turn it on and you should be connected.



  • Are you power cycling the cable modem each time you connect it to a new device?  Some of those cable modems have a habit of grabbing the first MAC address they are connected to and refuse to talk to anything else until you power cycle them.  That's the first thing I'd try to do.  If it still doesn't work, reply back.



  • @tim.mcmanus:

    Are you power cycling the cable modem each time you connect it to a new device?  Some of those cable modems have a habit of grabbing the first MAC address they are connected to and refuse to talk to anything else until you power cycle them.  That's the first thing I'd try to do.  If it still doesn't work, reply back.

    Right after I posted this I tried that and it worked! Before I just unplugged the modem for 30 seconds but, I needed to unplug the modem and take out the battery and unplug the server and take out its power supplies. After about 5 minutes with them off, I turned it back on and It got an IP right away and it works great!


Log in to reply