Problems with switch to AT&T fiber

[rung]

A bit of an unsubstantiated FYI, seeing varied reports of the BGW320-500 using the latest firmware, released recently, version 6.30.7 where the public IP address handed out by the modem to defined target passthrough device fails to renew via DHCP (DHCP-S) setting on the modem passthrough configuration. Current suggestion is to increase the Passthrough DHCP Lease to 1 day.

View attachment 63268

On the WAN setting on the router you might also want to adjust DHCP query frequency to one of the other two choices, and apply, if it becomes problematic.

View attachment 63269

Is that what happened? Back on 20DEC, I discovered in the logs that my router struggled for 12 hours to get a public ip. It finally got one and everything settled out as normal. I didn't notice it until I saw that my wireguard last login script logged a reset and logged into the router to investigate.


Rung

 

[aex.perez]

Is that what happened? Back on 20DEC, I discovered in the logs that my router struggled for 12 hours to get a public ip. It finally got one and everything settled out as normal. I didn't notice it until I saw that my wireguard last login script logged a reset and logged into the router to investigate.


Rung

If you have a 320-500, that’s on the recently pushed 6.30.7. Then very likely as it certainly fits within the timeline.

 

[rung]

If you have a 320-500, that’s on the recently pushed 6.30.7. Then very likely as it certainly fits within the timeline.

Yes!

Manufacturer HUMAX
Model Number BGW320-500
Software Version 6.30.7
Time Since Last Reboot 16:10:05:11

 

[howardmoon]

I did correct the lease time and disabled the firewall features as stated in the "how to use your own router..." link. Nice graphics @aex.perez, that should come in handy. Unfortunately, I'm still in the same boat. In desperation, I've tried disabling the router firewall, all of the AI Protection stuff and too many other things to mention or remember. I then tried to get some sense of what the failing sites have in common. I didn't, but here's what I've found:

Chrome and Firefox, no VPN

I can view the home page, but can't log in
att.com
sling.com
venmo.com
t-mobile.com
ecobee.com

Can't even see the home page:
Home Assistant site 192.168.1.9:8123. must be Nabu Casa related
Netflix: 'netflix.com took too long to respond'
in Chrome incognito I can see main page, slowly

these sites and many more work:
bank PNC
financial Fidelity
Amazon
credit card Chase
pharmacy Publix, Walmart
State Farm
Google: everything
Paypal: initially very slow, but can eventually get in

www.speedtest.net:
eternal "finding optimal server..."
"GO" does nothing

When I pop the cable back in my T-Mobile gateway all is immediately well.

 

[rung]

Here's the weird path I took but worked for me:
Reset router, reset gateway(mine was already reset)
Router must have detected the wan was 192.168.1.xx and changed default lan to 192.168.2.x
I went into gateway and changed its lan to 192.168.3.x and changed address to 192.168.3.1 and rebooted gateway
Changed router lan to 192.168.1.x and added a hostname to wan section
Rebooted router
Went into gateway (now 192.168.3.1) and changed to ip passthrough mode (my router hostname was on the pull down menu).
Rebooted router and the wan was a public ip

Edit: forgot to add that I also disabled wifi on gateway when I updated the gateway lan addresses.

 

[howardmoon]

I have factory reset the gateway twice and tried all the advice here, to no avail. What could cause such specific site problems every time? Is there any point in factory resetting the router?

 

[aex.perez]

Did the router get a public IP, or does it have the 192.168.2.1 address?

If it has the 192.x.x.x addresses then Passthrough is not configured correctly and is a big part of your issue with the sites you referenced.

If it has a 192.x.x.x address then you are in a double NAT scenario.

 

[howardmoon]

Keeps getting weirder. My T-mobile gateway has a local address and works. The AT&T one started with 99.29. This one, right?

 

[aex.perez]

Keeps getting weirder. My T-mobile gateway has a local address and works. The AT&T one started with 99.29. This one, right? View attachment 63301

Asas wan port having a 99.29.x.x. is what you want. Mine 99.150.x.x.

Point your browser here: https://whatismyipaddress.com/ should have that same 99.29.x..x address…

The use that 99.29.x.x here:
https://whatismyipaddress.com/ip-lookup and you should find it’s from AT&T

Next up, we can figure why you have your issues on certain sites, browser your using?

 

[sfx2000]

Keeps getting weirder. My T-mobile gateway has a local address and works.

That's normal for T-Mobile Home Internet - their GW will provide a RFC1918 local ip range for IPv4 -- 192.168.12.0/24 if I recall, and with IPv6, they don't issue a Prefix Delegation (IPv6-PD)

Works fine with their GW's for the most part, other than IPv4 is local, so gaming might be a problem, as the IPv4 address exposed is shared with many...

 

[howardmoon]

Asas wan port having a 99.29.x.x. is what you want. Mine 99.150.x.x.

Point your browser here: https://whatismyipaddress.com/ should have that same 99.29.x..x address…

The use that 99.29.x.x here:
https://whatismyipaddress.com/ip-lookup and you should find it’s from AT&T

Next up, we can figure why you have your issues on certain sites, browser your using?

Chrome regular and incognito 131.0.6778.205
Empty Cache and Hard Reload

Firefox 133.0.3

Is there some kinda cache, dns stuff etc. I can clear in the router?

 

[aex.perez]

Chrome regular and incognito 131.0.6778.205
Firefox 133.0.3

That should be fine, I'm same. Just need to double chek that the WAN address of the router is the Public IP. Did the URLs give you the Same IP as the router says it has and confirm it's from AT&T's allocation?

Also, just noticed, on your signature, "Asus GT-AX6000, Merlin 388.8_2 (x2)", does this mean you have/are using two of them?
Curious how you have connectivity setup, what plugs/connects to what?

 

[SirSherlockHolmes]

There's no actual Bridge mode, PassThrough is 99% close.

Assuming you setup Passthrough mode correctly on the AT&T BGW modem, and since you've (or the tech did) changing the LAN to 192.168.2.1 / mask 255.255.255.0

What you need to do on the Router: Set 192.168.2.1 for you, 192.168.1.1 is what I have because the Modem is set to 192.168.10.#/255.255.255.0 subnet (192.168.10.254 is my BGW modem)
View attachment 63225

And your DHCP settings to assign ASUS LAN IP's in the 192.168.2.# subnet, starting and ending address. LAN devices will get have 192.168.2.# (within the starting and ending range). I use 192.168.1.20-254 for my LAN IP's, remember in my case I chaged the Modem's LAN IP from 192.168.1.# to 192.168.10.# withem the Moden the haveing 192.168.110.254 as a result. This will get your LAN devices with 192.168.2.# addresses

View attachment 63227
Change the 192.168.1.1 to 192.168.2.1, reboot router, done

Again, in my case, changed the AT&T modems's LAN and kept 192.168.1.1 on the ASUS LAN side, my modem is 192.168.10.254 so I can get to the modem from the LAN. This will be the case for you, the modem management will be 192.168.1.254 from ASUS LAN devices with 192.168.2.# IP Addresses

For the AT&T modem MAC address used to enable PassThrough is the MAC Address of the WAN ethernet port on your router, and make sure it's set to DHCPS-fixed so that the WAN IP the router recieves from AT&T is a Public IP and stays fixed.

View attachment 63226

Assuming all correct, when you reboot the router the Network Map will show the public AT&T provided IP for the WAN (your routers) address, in my case 99.150.x.x and your authentication issue with your streaming providers will disappear. I'm suggesting you take a second look because the issues you're describing with the streaming providers is a common one if double NATted (PassThrough not configured correctly).

View attachment 63230

Good Luck, YMMV!

I only have my AX88u on the AT&T modem, WiFi radio's disabled on the modem as ASUS does a much better job, the Modem's firewall disabled too, again the router does a much better job, last thing. I have QoS on the router turned off/disabled, then again I have 1Gb and with it enabled it cut my over all bandwidth to 400Mb-500Mb and disabled ~940Mb in both directions.

I have a BE-88U, and am running a WAS-110 ONT-On-A-Stick directly into the SFP+ port, completely cuts out the AT&T gateway, and gives me a nice all in one solution without having to be stuck with AT&Ts equipment and NAT tables. Of course this options isn’t for everyone.

https://pon.wiki/guides/masquerade-...05-on-xgs-pon-with-the-bfw-solutions-was-110/

 

[howardmoon]

That should be fine, I'm same. Just need to double chek that the WAN address of the router is the Public IP. Did the URLs give you the Same IP as the router says it has and confirm it's from AT&T's allocation?

Also, just noticed, on your signature, "Asus GT-AX6000, Merlin 388.8_2 (x2)", does this mean you have/are using two of them?
Curious how you have connectivity setup, what plugs/connects to what?

Using "AiMesh", 2.5G between them.

"Use Ethernet cables to connect the LAN port of your main AiMesh router to the WAN port of each AiMesh node"