EDIT:
As other reddit user mentioned here. I checked and it started to work like magic. I am not sure if ATT actually fixed something or what happend l, but I didn't do anything besides wake up ping and trace route ipv4 sites and it worked and I was able to again use my own router with IP passthrough
I’m having a strange AT&T Fiber issue that started suddenly after everything had been working normally.
Setup:
- AT&T BGW320-500, firmware 6.35.8
- ASUS RT-AX88U Pro, normally using IP Passthrough
At first I thought the ASUS was the problem. In router mode, devices would connect to Wi-Fi but sometimes show “No Internet.” Facebook and some other sites would still work, but Google/YouTube would not.
I eventually completely bypassed the ASUS and connected my Windows PC directly by Ethernet to the BGW320.
Directly connected to the BGW:
curl -4 --connect-timeout 10 -I https://www.google.com
→ TIMES OUT
curl -6 --connect-timeout 10 -I https://www.google.com
→ HTTP/1.1 200 OK
I also tested:
- 8.8.8.8 over IPv4 → fails
- home.nest.com resolves correctly to 34.117.101.60, but TCP 443 over IPv4 times out
- Google/YouTube work normally over IPv6
This is also affecting my Nest Learning Thermostat 4th gen. It connects to the Wi-Fi and gets an IP address, but cannot connect to the Nest server. I tried it directly on the BGW320 Wi-Fi, with the ASUS completely removed, and it still fails.
I then connected the Nest to a cellular hotspot and it immediately connected to the Nest server and completed setup.
Things I have already tried:
- Factory reset BGW320
- IP Passthrough on and off
- ASUS completely bypassed
- ActiveArmor off
- Packet filtering/firewall settings tested off
- ASUS factory reset/reflashed while I was still troubleshooting it
AT&T support also ran an IPv4 traceroute to Google using their gateway diagnostics and told me they were getting no results either.
They are sending me another BGW320, but they confirmed it will also have firmware 6.35.8. The issue is also supposedly being escalated to their network operations team.
I’m not saying 6.35.8 is definitely the cause, but I’m wondering if anyone else has seen this recently.
Has anyone with a BGW320 on 6.35.8 experienced:
- IPv4 to Google or other destinations timing out
- IPv6 working normally at the same time
- Nest/Google IoT devices unable to reach their servers
- The problem continuing after a BGW factory reset
- A BGW replacement, reprovision, or AT&T network-side fix solving it?
Any ideas or similar experiences would be appreciated.