ATT Internet AIr
-
PROBABLY NOT GOOD IDEA TO EXPOSE THE GUI TO THE WWW
but its your call
-
-
@flat4 did I not gray/red out anything of importance ??? did I miss something important?
-
Check the DNS resolver settings, that can also be set in forwarding mode. It resolves directly by default though.
Try resolving something in the pfSense GUI in Diag > DNS Lookup.
Note what servers are responding in the failed WAN state. -
@stephenw10
I will check the failed state DNS resolution (from pfsense) later today when I am back on siteBut here are screenshots of the DNS Resolver. Should I just disable DNS Resolver ?
-
No I would expect that to work. It is in resolving mode and set to use 'all' interfaces for outgoing queries. So it should switch to use the WAN when the system default gateway changes.
-
@stephenw10
So do I not have the gateway for the Internet Air established correctly - ?Would there be any benefit for deleting the "interface" (it used to be a Suddenlink cable modem , before I added the Frontier fiber internet as WAN2)? And then recreating the interface and starting all over ??
I'm at a loss ... -
Unclear at this point. You need to run some DNS testing in the failed state to ind out what's actually failing.
-
@stephenw10
Ok so I got on-siteLooks like I can ping and access routes from pfsense and on the LAN
but I can NOT resolve DNS from either pFsense or the LANIt just hangs when trying to resolve a DNS
What can I post that will help to resolve this frustrating issue ??
THANKS
-
This post is deleted! -
These were attempts to ping form pfsense while in failed state - one to numerical address the other to name
-
So try to resolve google.com in Diag > DNS Lookup where all the configured DNS servers are tested.