ATT Fiber BGW320 - Has anyone truly been able to get IP Passthrough to work?
I bought the Deco routers to replace my aging Orbi routers which I had switched to being access points in the years past because they kept locking up.
My goal with this purchase was to use the Deco as my true router so I can have parental controls and change my DNS to an internal machine (PiHole) to block ads on the network.(The BGW320 does not allow custom DNS servers)
The problem I am facing is that the Deco router is not being given a true external IP address from the ATT Router, the "IP Passthrough" function does not appear to actually do anything.
On the BGW I have changed the following
1) disabled wifi
2) Turned off all firewall functions
3) Disabled packet filters
4) Enabled IP Passthrough
The Deco is still being served up a 192.168 IP address from the ATT router. Which is causing network slowness and the dreaded double NAT
Things that stand out
1) If you look online about this.... half of the posts say it's easy just set up IP passthrough. The other half say it's not possible.
2) I believe routers have 2 MAC addresses? The sticker on the bottom of the Deco state that the MAC address ends in "50" but in the BGW320 it sees it ending in "51". I've tried both. neither seem to work
Has anyone actually been able to get this to work? Or is it time to give up and return these Deco routers?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
1. Try rebooting BGW (disconnect power plug and reconnect) or your router.
2. Reboot the BGW, and say 20 seconds later reboot the router. This may vary slightly depending on how quickly the router boots up.
Again note I change the DHCP lease to 1 Day.
3. Worse comes to worse get the WAN IP assigned to the BGW-320 and assign it manually to the router. (I haven't seen the WAN IP change in over a year of AT&T fiber service, because the lease time is 24 hrs.
I suspect that if the router doesn't share it's MAC address when the BGW requests it, it automatically assigns a Local IP.
- Copy Link
- Report Inappropriate Content
I am having the same problem psuedo randomly. I only have a TP-Link Deco X55 Pro (AX3000) attached to the BGW320 (have tried the 5Gbe port and one of the 1Gbe ports) and it often will recieve an Address from the DHCP Pool instead of the WAN address. With only one device attached to the BGW320, I have tried setting to DHCPS-dynamic (so it gives WAN address to first device to do DHCP request) and I have set to DHCP-fixed and picked the MAC Address from the Device List (as well as copy/paste the MAC Address manually).
Regardless, if the BGW320 reboots, usually the Deco keeps it's WAN address but if I reboot the Deco, sometimes it will pull a local DHCP Address instead of the WAN Address. I cannot determine a pattern of why it does this but I know it happens because I have an app that I use that will complain of being double-NAT'd.
I "think" the problem started when I took an update to the BGW320 a couple months agon but I really am not sure. I did a factory reset on the BGW320 and re-setup to see if that would change anything and it did not.
I just had an idea though, I just went to the Home Network page and Subnets & DHCP tab and set DHCP Server Enable to "Off". In theory there now is no longer a Local DHCP server to hand out DHCP addresses. What is interesting is that now when looking at the IP Passthrough tab, I can make no changes to "Passthrough Mode" (it is set to Manual and Passthrough Fixed MAC Address) is set to my Deco's MAC address and greyed out.
Will leave like this and try rebooting a couple times.
I have no idea what will happen if I swap out the Deco and a new MAC Address shows up? Maybe it is set to DHCP-dynamic?
Anyone called into AT&T and try and get someone to review?
- Copy Link
- Report Inappropriate Content
@SteveMat For the most part I can get the WAN IP passed through by timing the reboots of both BGW320-500 and router, (as noted about 20 secs after the BGW starts I'll reboot my BE95. When I noticed update 6.30.7 installed, (completely under AT&T control), the timing was somewhat more finicky and I manually set the WAN IP on the BE95 for a while. Eventually I set it back to dynamically assigned and got the timing right...
No I did not contact AT&T because they won't support the third party router...
- Copy Link
- Report Inappropriate Content
See below for IP Passthrough page. Packet Filter is ON but when I went to the page none of the check boxes are checked...
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@SteveMat Really hard to say which side's hardware is at fault. And that is the exact reason that AT&T requires use of it's residential gateway.
If there's ever a firmware update, then I try to observe if the IP Passthrough works better. If it does then I guess it is that side hardware that caused the issue. If it doesn't improve then I tend to suspect the other...
What I can conclude is that when assigning the Deco an IP, if it doesn't read the selected MAC, then it assigns a Local IP. Who's firmware isn't following protocol properly, I couldn't say. It could be both....
- Copy Link
- Report Inappropriate Content
@jzchen When the gateway assigns a local IP to the Deco, does it not show, in its list of clients, the MAC address associated to that IP address?
- Copy Link
- Report Inappropriate Content
@yves_b Hmmm. Good question. I never thought to check. I believe it does. (I will definitely check next time the router gets a local IP).
Thank you for pointing that out.
- Copy Link
- Report Inappropriate Content
@yves_b It does, I have a screenshot in the BGW320 Home Network Devices Client list where it shows the same MAC address for my Deco with two different IP Address's (local LAN and WAN).
This is why I am thinking this is more on the BGW320 side, it would appear the DHCP request has the correct MAC address as it is associating it with an IP Address from the DHCP Pool. In the above case, I think I rebooted the Deco several times and it never pulled the WAN address. I think I went and pulled the ethernet cable and replugged in and that got it too work.
- Copy Link
- Report Inappropriate Content
@SteveMat Using the app's check for firmware updates failed tonight/this (very early) morning. I tried the reboot option in the app a couple of times but the LED didn't ever change colors, like it didn't reboot. I tried unplugging and plugging the power cord twice on the back of my BE95. I guess the LED is just a dummy night light it doesn't change at all upon power up. I tried 10 seconds, and then 30 seconds before plugging back in to realize this about the LED. Each time it still shows the 107 WAN IP successfully passed through.
(Shrugs).
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 2050
Replies: 31
Voters 1
