Wifi issue with page loading.
-
Hi all,
So this isn't post isnt specifically about connecting Wifi on the WifiInterface, I sadly don't have enough network ports left for a dedicated Wireless Link.
So the setup is 2.3.5, CARP setup master/slave.
BT Smart Hub (Bridged) -> pfsense FW -> Switch -> Wireless AP.
What I am experiencing is very weird behaviour when loading webpages, but only through the access point. I thought this was a problem with our old TP-Link access points, standard ethernet uplink, serving circa 10+ clients, N-300 capability… so I replaced them with a dedicated wireless AC Access Point with gigabit uplink to the switch, so the whole network backbone is gigabit minimum.
They still get the same problems on webpages. 5 second delay between click and full load/response etc making the system near unusable.
Here's the thing though... wire in instead of over the AP's, very little delay, webpages load very quickly...still admittedly not as snappily as i'd like, but orders of magnitude quicker.
DHCP is set on to IPv4, IPv6 traffic blocked.
DNS is configured using DNS resolver.
Override for DNS, from general setup is on.I just can't seem to eliminate this delay, any ideas?
Its stopping the users from accessing key systems in timely fashion.
I've done some searching around but non of the other solutions appear to be my issue.
Thanks in advance.
-
To help the narrow the problem down, I've got the following questions:
1) When you do a traceroute from WiFi connected client, where along the path does the slow down occur?
2) similar to 1) when you a DNS lookup using dig or nslookup using a WiFi client, is there a noticeable slow down before the DNS query is resolved?
3) Do ping times from the WiFi clients to the pfSense box look normal?
4) Are you using a relatively congestion free channel for the wireless AP?Hope this helps.
-
"Its stopping the users from accessing key systems in timely fashion."
So these key systems on on the internet or your network?
"Override for DNS, from general setup is on."
That doesn't really tell us what the client is using.. Out of the box pfsense would be using unbound - resolver and not forwarding. Letting your dhcp override what pfsense uses for its dns wouldn't have anything to do with what clients use for dns. Which normally would be unbound running on pfsense, which would then resolver and not forward.
tmaan222 question number 2 would be of interest for sure. Use your fav dns client nslookup, dig, host, etc. Try and resolve something www.google.com… After you get a response what was the time? Do it again you should get it cached answer that should be at most a few ms..
