ATT Internet AIr
-
@stephenw10 I'll have to retest and check the logs
And yes to fail - I just unplug the ethernet cord from the back of the frontier modem
-
@stephenw10
Here are the screen shots of the info
Apologies and thanks for help!!They start with states during failover
Show the DNS error on web browser
(the is with Forwarder Mode off under DNS Resolver settings)Then shows what happens after waiting for Frontier WAN to come back up
Ultimately would not fully connect and come back up untill full reboot of pfsense
-
-
@Gblenn
I have checked ALL for bothIs that correct?
-
Hmm, no DNS states shown there on states with ports starting with 53. You might need to filter differently to see that in the states.
I don't see the link state change in the logs there. Does it actually show the that when you reconnect the modem?
-
@ahole4sure said in ATT Internet AIr:
@Gblenn
I have checked ALL for bothIs that correct?
Yes that is correct, and I'm starting to think that ATT is actually blocking access to authoritative servers... If this is true you either have to stick to Forwarder mode, or ask ATT to stop blocking. I wonder if there is some setting you can change for your account perhaps?
On the fiber issue, there are a few things that stand out to me.
-
Gateway shows an IP but status is pending. So that IP is probably cached data in pfsense, the link is up (eth to frontier box) but pfsense has not verified the DHCP lease?
-
I notice you have IPv6 enabled on the fiber WAN. Could that cause issues? Try disabling it and see if that makes any difference when testing?
-
Have you tried pulling the fiber instead of the ethernet cable to pfsense? If that is possible to do?
Keeping the physical link up on pfsense interface thoughout the test... If there is something on that side that isn't really working as it should?
If you look at the dashboard instead of Status / Gateways, you will also see the negotiated settings for the interface. Does that seem ok, and is it the same before and after pulling and reconnecting the cable?
-
-
@stephenw10
Yes it does show this when I reconnect the Frontier fiber modem -- I will have to try it again this PM to try to get the states again
As far as ATT - wonder if @Gblenn is correct - I have been reading that ATT has some sort of DNS assist that could be hijacking my DNS queries -- not sure how to determine that.https://gist.github.com/CollinChaffin/24f6c9652efb3d6d5ef2f5502720ef00
@Gblenn
I will retest with IPv6 disableld tonight ! I see (after some ressearch) that ATT could be hijacking the DNS. I will look into this. Thanks -
Yes if they're redirecting DNS that would break the resolver.
-
@ahole4sure Why can't ISP's just leave things alone... I'm assuming, since you run the modem(s) in passthrough mode, that it's not in the device that is being blocked, or is it?
I'm thinking you need to log in to their portal (your accounts) to disable that "helper feature"... -
So am trying to leave things in situ as they have been setting and working (ie the ATT modems)
They are supposoed to be accesible from my LAN (and they were right after I re setup my pfsense) - via 192.168.2.1 and 192.168.3.1 (set in the device as the configuration addresses)
Through VIPsFor some reason I can't access either of those VIPs any longer --
I was trying to see if I could change the DNS settings we were discussing.
I can ping both 192.168.2.1 and 192.168.3.1 but can't access via web browser
-
Do you have outbound NAT rules in place for those?
-
Just auto
But looks like it’s there ????
-
Well it looks like you have conflict with the 192.168.2.10 VIP. You have that subnet on an internal interface too it appears since it's included in the auto rules.
You should also have manual rules to translate to the VIPs for traffic from LAN to the modem.
-
I think it is where I set up a static route trying to do what @Gblenn had suggested back in this thread previously
So the static route must have done the auto rule
Just so I don’t screw it up, after I have now deleted the static route, how should I set up the the outbound rule?
-
@stephenw10
So I got rid of the static route and then created the NAT rule ( ?? correct )Still get the error trying to reach 192.168.2.1
-
-
Will out seems that maybe disabling IPv6 might have fixed the problem with the frontier modem coming back online
After disabling. Came back online in secondsThere had been a support request sent to ATT about their DNS
After fixing NAT and being able to access the ATT modems config site - even after manually setting the DNS servers ( to non ATT servers) on fail over or attempt to utilize the ATT modem for internet access it just didn’t work unless DNS Forward Mode is checked in DNS Resolver
-
Nice. Yes those outbound NAT rules look correct now and no conflict is shown.
I would still try to capture the DNS traffic with the resolver enabled just to check it's actually trying to use the AT&T connection. A pcap filtered for port 53 would show that.
-
@ahole4sure Ok great that it works as intended when IPv6 is disabled. I have now idea why this is an issue other than I'm guessing something is not initializing as it should on IPv6 so it gets stuck. Perhaps @stephenw10 has some idea as to why this is and how to make it work fully, also with IPv6.
And on the DNS issue, I hope ATT comes back with a resolution that allows you to chose resolver mode as well.
-
Thank you guys for your continued help and putting up with me.
@Gblenn - I know it is semantics , but I have Resolver enabled but just have to check to "use Forwarding Moding" on that resolver settings page --- not sure what the difference is ??Also one other issue -- in my prior pfsense setup I was able to connect to 192.168.2.1 and 192.168.3.1 when connected remotely via my Wireguard VPN -- but now I cannot. Any addnl NAT settings for that to work? I have a Wireguard any rule in place and I have 192.168.2.0/24 and 192.168.3.0/24 as allowed IP's in my settings for my WG client
