no WAN after reboot | gets WAN if unpluging/pluging
-
I am running pfSense under Proxmox. I realised that whenever the device is restarted (power failure), the DHCP negociation times out. If I simply unplug then replug the cable, I do get an IP address.
The device is on an UPS and the whole thing is gracefully shutdown before reboot.
This question was asked under a one year old thread and I was suggested to start a new thread.
Here is the DHCP log
-
@ninthwave said in no WAN after reboot | gets WAN if unpluging/pluging:
If I simply unplug then replug the cable, I do get an IP address.
pfSEnse got nothing.
During more then 90 seconds, a DHCPREQUESTs, and DHCPDISCOVERs where send, no DHCP server (your ISP or upstream router) answered.
So, it took the last known 'WAN' IP, assigned that to itself.
This is risky, as your actual WAN IPs might be different.Btw : "Proxmox", or any other system for that matter, shouldn't go down for a power failure reason. If these might happen, use an UPS.
-
@gertjan said in no WAN after reboot | gets WAN if unpluging/pluging:
So, it took the last known 'WAN' IP, assigned that to itself.
This is risky, as your actual WAN IPs might be different.It does not get any IP until I unplug and replug the cable. No matter how long.
I also noticed that this only happens when the device is restarted. If I just shutdown the VM (pfSense) and restart it, then it gets an IP.
The problem arise when Proxmox itself is rebooted,
Any idea how further I can investigate ?
@gertjan said in no WAN after reboot | gets WAN if unpluging/pluging:
Btw : "Proxmox", or any other system for that matter, shouldn't go down for a power failure reason. If these might happen, use an UPS.
I do. When I say it gracefully shutdown, I mean it was on an UPS and everything went fine with NUT.
-
@ninthwave said in no WAN after reboot | gets WAN if unpluging/pluging:
It does not get any IP until I unplug and replug the cable
On the pfSEnse side, this triggers a DOWN and then an UP event. You can see these in the logs.
This event is used to start or restart the DHCP client.
This sequences is identical on billions of devices : as soon as the bits start coming in, which indicates there is a connection at a low (electrical or radio) level, higher protocol wake up to do their thing. The DHCP is often the first in lien, to create the IP stack.As you know, a network cable has two sides.
The other side of the cable is pugged in what ?
This device will also be subjected to a NIC DOWN and UP event.
This devices does it's work at that moment, and the classic DHCPREQUESTS and or DHCPOFFERS works right away == there is a communication.
Bridges or modems don't care about DHCPREQUESTS and or DHCPOFFERS, as they don't deal with this high level details. They transform light signals in radio signals, or phone line signals in ethernet packets. They don't do more.Question : when your conenction is up or ok, what happens when you release your (DHCP) WAN IP manually ?
That is :
Click the red button, wait 10 sec or so, and re click the same button.
Do the same test with the "Relinquish Lease" checked.This test just releases the lease obtained from the upstream DHCP server. The connection is still UP of course, but there won't be any IP traffic any more.
On the reconnect click, and IP is requested again, and everything goes on as usual.
This is how my pfSense works for the last decade. And I guess I'm not the only one. DHCP(client) is after all the default WAN 'protocol'.These two tests are executes without the presence of the hardware interface SOWN and UP events.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@gertjan said in no WAN after reboot | gets WAN if unpluging/pluging:
And I guess I'm not the only one.
I would just like to add this, pretty much it always works like this, except, for some DOCSIS stuff, specifically Cisco Edge QAM + some non-Cisco DOCSIS CPE + pfSense DHCP WAN
My parents' home has an APU4d4 which makes the pfSense feel + DOCSIS 3.1 from ISP
As long as I'm not spoof a CISCO MAC (on WAN) for DOCSIS modem, the ISP network refuses to DHCP IP to the APU4 stuff.
It's bullshit, but it exists
++++edit:
Yes the DOCSIS stuff, it's in bridge mode+++edit2:
still worth playing with... (RFC1918 / 192.168.100.1 DOCSIS modem)
-
@gertjan said in no WAN after reboot | gets WAN if unpluging/pluging:
Click the red button, wait 10 sec or so, and re click the same button.
Do the same test with the "Relinquish Lease" checked.IWith or without "relinquish lease", it releases the WAN and gets it back without problem.
-
@daddygo said in no WAN after reboot | gets WAN if unpluging/pluging:
++++edit:
Yes the DOCSIS stuff, it's in bridge mode
+++edit2:
still worth playing with... (RFC1918 / 192.168.100.1 DOCSIS modem)My ISP is Videotron and yes, it is a DOCSIS 3 cable modem.
I tried customer service yesterday but they told me : « We can see your modem is online and communicating so all is fine » To what I replied that : since I was talking to the clerk, yes the connection was alright... But I wanted help with how to configure my router for negotiating with the modem aftem the powerloss. No help.
Any suggestion on what I should try with DHCP client configuration tab ?
-
Run a packet capture on the WAN when it's failed so make sure pfSense is actually sending DHCP requests. See if anything at all is coming back.
Steve
-
Replying here on an old thread because I had the same issue. I made an account here just to reply for anyone in the future.
In my setup, I have my standard gateway DHCP all disabled, passthrough to the pfsense.
There must have been an IPV6 conflict on the WAN side pfsense, because after I disabled the IPV6 DHCP on the WAN adapter, the issue went away.
