pfSense English Support > DHCP and DNS

No WAN IP since 2.4

(1/3) > >>

mcfly9:
Hello,

Ever since updating to 2.4.1, I am not getting a WAN IP after my cable modem reboots. Tried release/renew IP, rebooting pfSense but no luck.


--- Code: ---Nov 9 19:56:42 dhclient 21222 hn1 link state up -> down
Nov 9 19:56:46 dhclient 21222 DHCPREQUEST on hn1 to 192.168.100.1 port 67
Nov 9 19:56:47 dhclient 21222 DHCPREQUEST on hn1 to 192.168.100.1 port 67
Nov 9 19:56:47 dhclient 21222 hn1 link state down -> up
Nov 9 19:56:47 dhclient 21222 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:56:47 dhclient 21222 DHCPNAK from 10.229.0.1
Nov 9 19:56:47 dhclient 21222 DHCPDISCOVER on hn1 to 255.255.255.255 port 67 interval 1
Nov 9 19:56:47 dhclient 21222 DHCPOFFER from 10.229.0.1
Nov 9 19:56:47 dhclient ARPSEND
Nov 9 19:56:49 dhclient ARPCHECK
Nov 9 19:56:49 dhclient 21222 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:56:51 dhclient 21222 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:56:56 dhclient 21222 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:56:56 dhclient 84434 connection closed
Nov 9 19:56:56 dhclient 84434 exiting.
Nov 9 19:56:59 dhclient 60445 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:57:01 dhclient 60445 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:57:05 dhclient 60445 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:57:09 dhclient 60445 DHCPREQUEST on hn1 to 255.255.255.255 port 67
Nov 9 19:57:15 dhclient 60445 DHCPDISCOVER on hn1 to 255.255.255.255 port 67 interval 2
Nov 9 19:57:17 dhclient 60445 DHCPDISCOVER on hn1 to 255.255.255.255 port 67 interval 2
Nov 9 19:57:19 dhclient 60445 DHCPDISCOVER on hn1 to 255.255.255.255 port 67 interval 5
Nov 9 19:57:24 dhclient 60445 DHCPDISCOVER on hn1 to 255.255.255.255 port 67 interval 8
Nov 9 19:57:28 dhclient 61193 connection closed
Nov 9 19:57:28 dhclient 61193 exiting.
--- End code ---


The only way, I was able to get a WAN IP was to power off my cable modem and pfsense as well, power on the modem, wait for it to boot and then boot pfsense. If I reboot pfSense after this, I still get (the same WAN IP) and also release/renew works fine, even with relinquishing the IP.

I have no problems with the same configuration on 2.3.5.

Any ideas why this might be happening? My theory is that upon rebooting my modem, first it boots with a dhcpserver assigning an ip in range 192.168.100.x, before toggling the WAN link and assigning a valid WAN IP. Somehow pfSense doesn't like this and won't pick up the newly offered IP.
 

xrnd88:
I'm having the exact same issue. Did you find any way to resolve this?

mcfly9:
No, I am starting devices in the correct order to work it around. This makes it quite impossible to connect to the network remotely once it went into a bad state.

xrnd88:
yeah it's a pain. My temporary solution is a script that reboots the pfsense box if the network has been down for 20 minutes.

mcfly9:
Any changes in 2.4.1 / 2.4.2?

Navigation

[0] Message Index

[#] Next page

Go to full version