Not picking up WAN IP address from Cable Modem
-
@nollipfsense Thank you, that seemed to work. Took me a bit to work out how to connect to the LAN interface, for some reason I could only connect through the OPT1 interface, for some reason I couldn't get an address from the LAN port even though they were both setup for DHCP.
Now to play around with the rules so I can get access to the www lol :) again thank you
-
@gherkin12
Hey, I try the very same thing, and everything seemed to work, but why when I restart the computer, it waits 15 minutes? Can I change the settings back after the connection is made -
@mattpdx86 You only add the 15mins if and only if you're not getting a WAN IP with the default time setting.
-
Mmm, that seems like a different problem if it connects after 15m with the default settings. In 2.7?
-
@stephenw10
It gets the ip address after I added the 15 min timeout. I am using Pfsense Plus 23.05.1 -
Ok, we'd have to see the logs without that added to why it was failing to pull an IP address. Usually though it's because the WAN NIC was not linked when the dhcp client tries to run. And that is usually because the upstream modem device takes longer to boot when both it and pfSense are rebooted.
-
@stephenw10
I tried to use another machine, but it failed to pick up an IP address all together -
You tested using pfSense in different hardware? Do the logs show it trying and failing before the WAN link comes up?
The 15min timeout should just allow it to keep trying for 15m, not be forced to wait 15m before connecting.
-
@stephenw10
Had issues getting onto the LAN to access the web configurator to get to the logs. It was a Dell OptiPlex 3010 with a Realtech network card and I was having the same issues but the HP ML110 G7 worked with 2 Intel NICS. This is confusing and I don’t know who I am having this issues. -
Mmm, Realtek NICs can cause problems but link delays are not usually one of them. If Intel NICs work though stick with them. Intel NICs are almost always the best choice.
