LAN client connection delay
PFsense 2.4.4 simple setup to replace ISP router rental. IPv4 only, DHCP used for wireless AP clients and hardwired LAN for desktop computers with static IP addresses.
When any of the desktop computers boot up and into windows, there is a delay (15 seconds, which feels like an eternity when you run to quickly look something up) before the network connection is operational.
On the old ISP router this was nearly instantaneous upon logging into windows.
Can I fix this?
KOM last edited by
Does nothing work during that time or are you just looking at the tray icon?
Nothing works, not even a ping to the PFsense box.
But I know what you mean, because the connection comes alive before the tray icon changes its image.
I would check for partial IPv6 connectivity. That can present in odd ways.
If your ISP provides any IPv6 but either not suitable for use or incomplete or pfSense is just not configured correctly your clients may be trying to use it and have to time out.
If you're not using IPV6 I would disable it in pfSense at least as a test. That means disbling the DHCPv6 server on LAN. Then setting the LAN interface v6 type to none then setting WAN to none.
disbling the DHCPv6 server on LAN
DHCPv6 server was already disabled, if I'm doing this right I went to Services -> DHCPv6 Server & RA and upon going there I get an error message: The DHCPv6 Server can only be enabled on interfaces configured with a static IPv6 address. This system has none.
I went into my LAN config and IPv6 Configuration Type was set to none. WAN interface IPv6 type was set to DHCP so I set it to none.
This does not seem to have had any impact on the issue however.
Check the logs? Anything in the system log showing a load of activity when the client connects?
Does the DHCP log show it issuing the new lease before the delay happens at the client?
yeah half-in IPv6 can introduce delays like that.
Disable the DHCP6 server on LAN
Edit LAN and change IPv6 track interface to None.
Edit WAN and set IPv6 to none.
Alternately, and probably preferably, get with the ISP regarding where they are in IPv6 deployment and get it all turned up correctly.