ATT Internet AIr
-
Ok, good. Well with that that one device should work at least.
So to confirm you are still passing the LAN address to clients for DNS?
-
Thanks for hanging in there and helping! Need to buy you a big cup of coffee!
Not sure I understand what you mean with your question. Sorry
-
In the LAN DHCP server config have you entered any DNS servers to pass to clients when they pull a lease?
If you don't enter anything there it will pass the DHCP server address (LAN address) to clients to use for DNS by default. That means they use Unbound in pfSense which should work on both WANs.
If you passed, for example, 8.8.4.4 or 1.1.1.1 that can only work via one WAN.
-
This post is deleted! -
So I’m on my iPhone so it not great screenshots
But here are my LAN DHCP server settingsShould I change something? It’s kinda greyed out but DNS is listed as 192.168.1.1
-
-
-
Ok, so it's passing the LAN interface. That should be fine for anything that uses it. That one client is hard coded to use 8.8.8.8.
The root issue here though still seems to be that Unbound in pfSense is not using the WAN connection when WAN2 is down. I think you will need to test on site though.
Try setting up another failover group that has WAN as the tier1 gateway. Then try setting that as system default and retest. In that situation Unbound should already be using WAN when WAN2 is disconnected and should continue to work. It should also failover to WAN2.
-
@stephenw10
Back on site
Set up the second test gateway group
WAN as Tier 1 , WAN2 as tier 2When I set the test group as default, it switched to WAN ——- no internet/ DNS
Switched back to other gateway, internet/DNS returned without reboot
-
Hmm, were you able to see DNS traffic on WAN in the states?
Starts to look like the WAN connection just blocks or intercepts DNS for some reason.
You can try to test that directly from the pfSense command line with something like:
dig @8.8.8.8 netgate.com -b 192.168.2.2 -
@stephenw10
No joy directly from command line!If I knew for sure another failover device/method would for sure work I would consider returning the Internet Air devices - lol
Now it's just irritating that this is so difficult (esp with expert help like you)
-
Did the WAN IP change from 192.168.2.2? By binding to that address the query is forced to use the WAN.
-
@stephenw10
OMG, sorry
I'll have to get back on-site this afternoon - looks like the WAN device went offline or something
-
Ah, that would do it.
-
@stephenw10
Got back on site and restarted the WAN
It is back up and going on 192.168.2.2
If I do the test gateway group , I am still losing DNS/Internet with WAN as Tier 1 and primary internetBut I did get differnt result with the command line
see below
-
Hmm, well that looks OK. Try setting Unbound (DNS Resolver) to forwarding mode so it uses the configured remote DNS server directly. You should also disable DNSSec whilst testing that.
-
Just wanted to chime in here and mention that I have been using pfSense with AT&T Internet Air in failover configuration for about a year now without issues (primary WAN is fiber). During that time I have not observed any evidence that DNS might be intercepted somehow on the Internet Air side - DNS is working fine for the failover gateway group I've got setup with Unbound in resolver mode. So I think in this case it's still a misconfiguration somewhere in the pfSense settings.
What do you have set for
DNS Server OverrideandDNS Resolution Behaviorunder General Setup?Also, this section in the pfsense docs will be good to review if you're switching over from resolver to forwarder and using multiple wan connections:
https://docs.netgate.com/pfsense/en/latest/multiwan/interfaces-and-dns.html#dns-configuration
Hope this helps.
-
@stephenw10 @tman222
Ok so I'm not completely sure which setting fixed things BUT by setting DNS Resolver to forwarding and disabling DNSSec - the WAN (ATT Internet Ait ) Internet worked when enabling the Test Gateway group1@tman222
I attached screnshots of my settings - how does that compare to yours? Do you have the Internet Air setup on a seperate "local" subnet like I do? Shame it doesn't have a full "bridge mode". Also I could not seemingly get DMZ to work in that with it enabled my pfsense interface still shows the local IP address - it doesn't pass through the public IPThe screeshots show the active test gateway. The command line results AND the succesful "speedtest" (shich was never accesible before) with the test gateway and then the regular gateway. AND my general setup settings page for @tman222 question
How should I permanenetly set things ? Any explanation or thoughts on what is happening?
-
-
