Specify a static route on BGW320-500 to attached router?

Cascaded router is actually intended for a Public Static subnet, but it has been suggested in the past for your use case.  

AT&T has [sarcasm], in its infinite wisdom, [/sarcasm] decided that it can reserve the entire private 10.0.0.0/8 address block for its own use for CGNAT and won't allow its Gateway devices to accept those addresses in configurations.  I think that's what your issue is, and I don't see any way around it.

You can't add static routes in the BGW320.

With your specific limit of a network of 10.100.0.x. for your secondary network is to use IP/Passthrough mode in the BGW320.

Do you need instructions on how to setup IP/Passthrough mode to allow your 10.100.0.x. based router to receive the Public DHCP address that is shared with the WAN port of your 10.100.0.x. network?

Dave

Thanks. Right now I'm providing private and guest SSIDs from the BGW320.  My intention was that clients on the private SSID (as described above) could reach the network managed by the external router, whereas clients on the guest SSID are on their own isolated subnet and cannot reach that resource.  If I enable IP passthrough, it's not clear to me I could accomplish that.  It sounds like if I can't move off the 10.0.0.0/8 network, this setup isn't possible without introducing a separate wifi AP.

Hello Guys,

I have the same problem with BGW320. I am doing the same thing as described, I have a router BGW320-500 connected to the ISP via ONT, and its LAN network is 192.168.1.0, I connected another router NETGEAR to the BGW320-500 router with a subnetwork 10.0.0.0. What I wan to do is: devices on the primary LAN (192.168.1.0) can ping devices on the NETGEAR LAN (10.0.0.0). The only possible way to do that if I am not mistaken is to setup static routes from the BGW320-500 router, (192.168.1.X --> 10.0.0.0) which 192.168.1.X is the ip of the router or the gateway of the primary LAN. But this router doesn't have this option, I wonder why. I don't wan to use IP/Passthrough, it's not the same as static routes. The NETGEAR router has this option, if it were my primary router, my problem would be resolved. Sometimes old versions of devices offer more common senses functionalities and features than the new ones. I think BGW320-500 must downgraded its version.

There is nowhere in the BGW320 interface to set up static routes.   There is no way to send traffic from the "Gateway" subnet to a private network address behind a router attached to the Gateway.

So the company that designed BGW320 router should of think about it, cause NETGEAR has this feature.

Don't hold your breath waiting. They haven't felt the need so far. 

Lol, ok thank you for your time.