upgraded to pfsense 2.8.0, WiFi devices report intermittent 'no internet access'
-
@skubany2 said in upgraded to pfsense 2.8.0, WiFi devices report intermittent 'no internet access':
I was testing host name vs IP.
Make sure you use the full hostname with the domain. Without that Windows will (probably) add it's own domain which may or may not be correct.
-
@skubany2 said in upgraded to pfsense 2.8.0, WiFi devices report intermittent 'no internet access':
Adding secondary DNS (of the other interface) under each interface's DHCP Server may also be needed.
Why would you think you would need to do that.. What would be the point of handing your clients 2 different IPs on pfsense? If pointing them to stuff other than pfsense. How would they resolve your local resources?
If pointing to 1 local (pfsense) and 2nd other outside dns like googledns or something you have no idea which one it might ask.. Such a setup is always asking for having a bad day at some point.
I capture packets on the LAN interface I see LLMNR (Link-local Multicast Name Resolution) requests and NBNS (NetBIOS Name Service) requests for the host name
That would only ever be able to resolve hosts on the same network as the guy asking for it.. Those would not resolve some host on some other network.
-
@johnpoz
"secondary DNS"
Under LAN DHCP Server I would have the LAN IP as primary DNS (default) and WiFi IP as secondary DNS.
Under WiFi DHCP Server I would have the WiFi IP as primary DNS (default) and LAN IP as secondary DNS. -
Yeah, there's really no point in doing that. You are just accessing the same server via two addresses it's listening on.
