Have to restart netwok PC's before internet available
-
Hi guys
I am just testing the 2.0 build, no matter which version i use i have found that my PC will not get an internet connection unless it is restarted if the PFsense machine started last. This is weird since PFsense can check for, and download updates while this happens.
Though not a massive barrier, it would be great to stop this if it is just a setting somewhere, would anyone have any ideas? DHCP is set up as a server on the LAN connection if its any help.
-
If the pfsense box is your DHCP, and your PC is up and running before the pfsense box, then your PC won't have IP. (Unless you've went into the PC's settings and made it static)
2 easy ways to get a new IP, unplug the ethernet and plug it back in. Windows you can go to Start > Run > CMD > ipconfig /release |enter| ipconfig /renew |enter|
linux you can just bring the adapter down and back up.
Hi guys
I am just testing the 2.0 build, no matter which version i use i have found that my PC will not get an internet connection unless it is restarted if the PFsense machine started last. This is weird since PFsense can check for, and download updates while this happens.
Though not a massive barrier, it would be great to stop this if it is just a setting somewhere, would anyone have any ideas? DHCP is set up as a server on the LAN connection if its any help.
-
I windows you may have to use
ipconfig /release * ipconfig /renew *To make it happen properly
It can also be done in the Windows GUI and not just the cmd prompt. On XP you can "repair" the interface, and Vista/7 have a diagnose feature which also resets the NIC and pulls DHCP again. Or you can always unplug the cable from the workstation for 10 seconds then plug it back in.
Other operating systems will behave differently of course but should be something generally involving resetting an interface or bringing it down and back up again.
-
Thanks, this helps, but why does it only do this with PfSense? The router I was using before would be ok when restarted while my PC was on…
-
That should happen with any DHCP server, really. If the DHCP server is down when a PC boots up, it can't pull an IP so (at least with Windows) it gets stuck in the link-local autoconfigure subnet.
If you reboot pfSense it shouldn't happen (and doesn't for mine or any other box/vm I've ever touched), it should only happen if the firewall is off when the PCs boot.
If you had a little linksys or similar box, you may not have noticed before because those boot up very fast. pfSense can take a while to get booted up all the way.
-
Sometimes, my windows PC will do something like this…
I get an extra 0.0.0.0 in gateway but I can still contact pfsense. For example:
Lease Obtained. . . . . . . . . . : Wednesday, February 16, 2011 3:15:37 AM
Lease Expires . . . . . . . . . . : Thursday, February 17, 2011 3:15:41 AM
Default Gateway . . . . . . . . . : 0.0.0.0
192.168.100.1
DHCP Server . . . . . . . . . . . : 192.168.100.1
DHCPv6 IAID . . . . . . . . . . . : 335551526
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-0D-06-27-00-17
DNS Servers . . . . . . . . . . . : 192.168.100.1
NetBIOS over Tcpip. . . . . . . . :I always thought it is my PC but it could be due to external factors...
-
Like Jimp said, pfsense can load just a touch slower than other installations. What may have been happening before is the previous installations you used before (linksys/netgear/m0n0 etc…) would boot up before your computer gave up trying to get an IP and assigned itself the 169 address. Once your machine gets that 169 address, it gives up trying to get an IP, thus you have to release/renew.
Maybe you can increase how long your PC tries to get an IP through a registry tweak if this concerns you. Otherwise turn the pfsense box on first, give it a 30 second head start and then turn the PC on. Or leave the pfsense box on 24/7 :-)
Thanks, this helps, but why does it only do this with PfSense? The router I was using before would be ok when restarted while my PC was on…
