Cannot get WAN IP on reboot.



  • Every time I reboot pfsense I have to release and renew the WAN IP lease in order to get one.  I have done the following;

    Rebooted my cable modem multiple times.
    I've made a firewall exception.
    I've even called Cox and talked to their supposed tier 2 support.
    I've switch the NICs around.  re0 was WAN, now re1 is WAN.
    I've checked the BIOS and there are no configurations for the NIC. re0 is onboard, and re1 is PCI-X.
    I have witness it a few times get 192.168.100.1 from the modem.
    I am also rejecting leases from 192.168.100.1.

    Your help would be very much appreciated.



  • Any chance you could monitor the connection between the modem and firewall?  It helps to know what's happening.  To monitor the connection, you can get a cheap managed switch confiugred to port mirror.  You can then use a computer running Wireshark to see what's happening.  If all is working properly, you should see a DHCP discovery, offer, request and ack.  If you fail to see any of those, it will provide clues as to where the problem is.  Also, have you tried connecting a computer to the modem, to see if it gets an address?  That could help determine where the problem is.



  • Can't pfsense monitor the interface?  I've not tried the PC yet, that will take some doing, but possible.



  • @razorbackgeek:

    Can't pfsense monitor the interface?  I've not tried the PC yet, that will take some doing, but possible.

    Given that the problem occurs when rebooting pfSense, it would be difficult to set up Packet Capture to monitor the connection.



  • Good point.



  • What I have done now is plugged a Win7 box directly into the modem and it too would not get an IP.  I rebooted the modem several times and Windows managed to get 192.168.100.1 all on it's own.  Finally after a release and renew it got the WAN IP.  I'm going to install Kali Linux on my laptop tonight, and investigate further.



  • Given that the problem also occurred with Windows indicates it's a modem problem, not pfSense.  However, a work around may be a shell script that forces a release/renew, at a minute or 2 after port comes up.



  • Great, guess I'll try my hand at shell scripts.


Log in to reply