WAN link not coming back up after cable modem comes back up from connection loss



  • I have had this problem on and off for the past year or so. I am on 2.1 x64 and was on 2.0.3 x64 before and had same issue. Whenever my cable modem (Charter) losses it connection my pfsense box does not always reconnect. The only fix I can find is to bounce the server. I have tried unplugging the cable and plugging the cable back in and doesn't work. I found another thread on the issue https://forum.pfsense.org/index.php/topic,59546.0.html Which they said replacing the NIC fixed the issue. I tried this with an  Intel PRO/1000 PT Dual Port Server Adapter. I moved my WAN and LAN connection to this card and still have the issue. The original NIC's was a dual Intel 82574L on the mobo of a Supermicro SYS-5015A-EHF-D525.  I found another thread https://forum.pfsense.org/index.php/topic,53221.0.html and it looks like they never found a fix. Mainly just talking about DHCP not renewing. I do not have any logs at the moment to post because I had to bounce it. When I have this problem again I will try to post the logs. I assume it will show something similar to the last link talking about DHCP. Does anyone have a fix for this or a way to tell DHCP to restart after losing the connection?



  • Not sure if this is a fix for you, but I had the exact same symptom with charter and thier supplied modem. I had to go into the WAN interface (Interfaces > WAN) and under "Reject Leases From" I had to enter the IP of my modem (192.168.100.1).

    It seems when its being rebooted and not established with the ISP yet, its giving an IP of 192.168.100.1 to pfsense, then all sorts of stuff gets messed up. It took me many times of rebooting both modem and pfsense before it would work. #pfsense IRC channel gave me this to try and it worked perfectly.

    Modem boots up and pfsense gets the IP right away.



  • Thanks for the help! I will try this and post back the results.



  • did that solve your problem?



  • Yes, fixed my problem. haven't had to reboot since. Thank you!