ATT Internet AIr
-
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.
-
So I have tried as recommended - still nothing. It's like the system gets "stuck" when I try the DNS Lookup after fail state begins. And to make matters worse the more changes I make now, it appears that coming back out of the failed state requires reboot of the pFsense to get things working for my main WAN and internet source.
I am a loss now as to how to even troubleshootGonna try to call ATT today - I wish I could get a way to put ATT modem in bridge mode. As maybe mentioned before, I have DMZ set to the dhcp (later set to static) address of 192.168.2.11 that the ATT gateway/modem gave my pFsense box - yet it still shows the local IP of 192.168.1.11 in pFsense dashboard. I was hoping that it would show public IP. Not sure that it has anyhting to do with the DNS issue though.
-
Hmm, is it possible it's blocking or intercepting DNS traffic?
Check the state table in Diag > States when the main WAN2 is down and you are trying to resolve something. You should see the udp port 53 connections using the WAN.
Did you try changing the kill state on gateway failure setting?
-
@stephenw10
So it does appear that somehting is blocking things, looking up this SYN_SENT CLOSED errorThoughts on how to fix?
-
@stephenw10
Other weird thing is that during the failed state , while on the LAN, I can bring up a google web page and sucessfully google something and it will bring up a page sucessfully -
There are no DNS connections shown there.
Try setting All interfaces and filtering by:
:53Make sure there are at least some on WAN and they're not all on WAN2.
Did you try the state kill setting?
-
@stephenw10
I am baout ready to pull my air out - lol
I can't get anyone that speaks english (my primary language) from ATT support and what's worse nobody that knows what "bridge mode" is.I reverted my Internet Air back to the original factory 192.168.1.1 address
Then changed it to 192.168.1.155
That then gave my connection form the LAN of the Internet Air to the WAN configured interface of the pFsense an IP of 192.168.1.156
Setup the gateway and the gateway groupWhen pulled the ethernet cord on the WAN2 it goes to failed state as it should
Still NO DNS -- I have attched the STATE you mentioned filtered for 53
The crazy thing is that despite the setting the state kill setting I still have to reboot the box inorder to get internet / DNS back after the failed state is corrected
I'm at a complete loss - ugh
-
Ah, it looks like your LAN is also using 192.168.1.0/24?
if
That's a subnet conflict between WAN and LAN. You need to change one of those to a different /24 subnet. That obviously wouldn't be a problem if you had a public IP on WAN.However it's also different to when you set it up above where the WAN was using the 192.168.2.0/24 subnet.
-
@stephenw10
Ok I can change back to 192.168.2.0but we were running into the same issue there as well??
Also - question -- when I create the interface connection and set up as a DHCP connection for the created WAN it seems to create some "dummy" gateway (that is greyed out and not available for use in the gateway group area). Do I just create an additional gateway ? Or how to handle that?
-
Change it back. Any tests with the subnets conflicting will definitely fail an just confuse matters.
We want to see DNS states on the WAN, without being NAT'd, and check if there are any reply packets.
Is your outbound NAT still set to automatic?
-
@stephenw10
yes automatic re outbound nat -
-
@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 DNS
-
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?
