Dhcp expected behavior?
-
On a vmware setup…
On 1.2.3 if my wan side was down the ip is shown as 0.0.0.0. When the connection comes up, it eventually gets the ip and I am back in business.
In 2.0 if my wan side was down, the ip is shown as 0.0.0.0. When the connection come up, it never seems to get the ip.
Is pfsense 2.0 waiting for a link state (which it will never get on the vm). Or did I just wait long enough (waited 10 minutes and that seems to be a long downtime as it stands anyways).Final question. How can I check the WAN dhcp lease time. Googled it but cant get any command to work.
Thanks!
-
Final question. How can I check the WAN dhcp lease time.
On my pfSense system, console or ssh session:
clog /var/log/system.log | grep dhc | more
Jul 22 07:44:04 pfsense2 dhclient[41010]: DHCPREQUEST on vr0 to 192.168.211.173 port 67
Jul 22 07:44:05 pfsense2 dhclient[41010]: DHCPACK from 192.168.211.173
Jul 22 07:44:05 pfsense2 dhclient: RENEW
Jul 22 07:44:05 pfsense2 dhclient: Creating resolv.conf
Jul 22 07:44:05 pfsense2 dhclient[41010]: bound to 192.168.211.217 – renewal in 3600 seconds.
Jul 22 08:44:05 pfsense2 dhclient[41010]: DHCPREQUEST on vr0 to 192.168.211.173 port 67
Jul 22 08:44:06 pfsense2 dhclient[41010]: DHCP from 192.168.211.173
Jul 22 08:44:06 pfsense2 dhclient: RENEWDHCP lease time = 3600 seconds.
(Only the WAN interface gets its IP address from DHCP; if you have multiple interfaces getting their IP address from DHCP you will have to apply additional filters. Another option is to look in the appropriate DHCP server configuration.)
-
much appreciated! Guess i just need to wait for the renew request to find out, as I cleared the log looking for it yesterday.
Played some more and as long as the cable is connected, it will look for a dhcp. I think it was my testing that was at fault. Now if I just knew when it would renew…. I just need some patience. I thought it would be in a config file or a status page (should be).