ATT Internet AIr
-
Here are some pics of where I changed back to 192.168.2.0/24
And the 53 filtered state
login-to-view login-to-view login-to-view login-to-view login-to-view
-
@stephenw10
Sorry for being a pain in the butt -- but the really bad issue is that I can't seem to find a work around to get things working after the "fail" without literally rebooting the pfsense box!! Makess testing so hard -
Ok, two odd things there.
You fail to get any ping replies from 8.8.8.8 when pinging from WAN. That should work.
There is DNS traffic from WAN directly but the states show it's still being outbound NAT'd from it's own address which should never happen.
On the outbound NAT page what rules are shown for the auto generated rules?
-
-
Hmm, that looks OK.
You have NAT states showing 192.168.2.2 being NAT'd to itself just on a different port. That normally wouldn't hurt DNS but it also shouldn't happen so it's unclear exactly what it's doing.
What happens if you reboot with WAN2 disconnected?
-
@stephenw10 So attached are shots where rebooted with WAN2 disconnected
Still no DNSlogin-to-view login-to-view login-to-view login-to-view login-to-view
-
Ok. So there is no DNS traffic on WAN there.
There are clients that are configured to use 8.8.8.8 directly, 192.168.1.79 there, but it appears 8.8.8.8 is statically routed via WAN2 so it's failing.
Check the routing table in Diag > Routes.
That would usually be either the gateway monitoring or in the general setup if 8.8.8.8 is configured as a DNS server.
In your previous screen shots you have 8.8.8.8 used on WAN for both those but it looks like something has changed because it's being forced via WAN2.Is 192.168.1.79 a client you're testing from?
-
@stephenw10
So I am attaching the Diag > Routing tableI am attaching my current setup for my interfaces / gateways
And my current setting in the General Setup DNS pageLastly I am attaching what I thought / hoped might work form a Protectli support page for setting up LTE modem on thier devices (in the Advanced Settings of the LAN Rules - forcing it to use the Failover GW
But this AM tested and it still failed -- AND had to completely reboot to get internet back up and going once the main WAN2 was plugged back in!
login-to-view login-to-view login-to-view login-to-view -
-
-
also btw, I am not sure what .179 is
it is not the device I'm testing form - but the network is large with probably more than 50 or 60 devices connectedThe routing table does not gicve the device a name (like many have) - it just gives a MAC address
-
Ok you have some conflicting settings there. You have DNS servers set with specific gateways and you also have the same DNS servers set as monitoring IPs for the gateways. Both those thing add static routes and must match to work correctly.
In your setup you don't need to set gateways on the configured DNS servers because they should work on either WAN and you're using a failover group as the default gateway. Additionally your are resolving directly so the DNS servers configured there are only used as a backup. However the conflicting static routes still breaks DNS for anything trying to use those servers directly. So remove the gateway settings from the DNS servers on the general setup page.
If you add a failover group to the pass rules on LAN you bypass rules for local traffic. That includes DNS traffic from LAN side clients to the LAN interface. Otherwise it will be forced out of the WAN and never reach Unbound in pfSense.
-
Ok. Thank you for advice
I’ll change the DNS settingsSo do I leave the advanced LAN rule like Protectli recommended or change back to not using. I’m sorry I wasnt clear …
-
This post is deleted! -
@stephenw10
Here is the new routing table after removing the DNS static routeslogin-to-view login-to-view -
Hmm, well I still expect to see the gateway monitoring IPs there, did you remove those too?
Anyway that device at 192.168.1.79 should work fine trying to access 8.8.8.8 directly.
I'm assuming (because it's the default) that your LAN side clients are being passed the LAN interface address to use for DNS?
-
@stephenw10
I didn't change the monitor IP's on the gateways
??
Is this what you were referring to?
login-to-view login-to-view -
I'm not on site until Tuesday - not sure how to safely test while being remote (unless you have ideas on how to "fail" the main internet and not lose connection ??
-
Hmm, I expect to see static routes for 8.8.4.4 and 1.1.1.1 unless you have checked the box to not add them on the gateway config page.
You may need to resave them to add those routes. Though not doing so should not affect DNS.
If you have the DMZ feature setup on the AT&T router you should be able to access the WAN remotely as long as rules allow it. However I'm not sure I would want to try disconnecting WAN2 without being on site to recover it if required.
-
@stephenw10
Weird -- might even be a part of why I need to reboot after a failed state
BUT. I had to completely reboot the box to get those static routes to show back up (the monitor IPs). Resaving the interface settings , restarting the service , etc - nothing brought back the expected routes until I rebooted the box