Let AT&T help you elebrate your dad with Father's Day Gifts that connect us.
Get superfast AT&T Fiber internet
adac-solutions's profile

Tutor

 • 

49 Messages

Monday, July 4th, 2022 7:09 PM

BGW320-505 ATT Fiber Cascade Routing Configuration with /29 block on PFSense

I recently started having trouble with my internet getting intermittent latency and 10 - 20% packet loss.  They sent a tech out who was super friendly.  They gave me a new router (BGW320-505).  This replaced the original router I've had for about 7 years the 5268AC.

Previously I had to do source pings to get my individual 5 static IP addresses working.  I also was using a static IP address on the pfesense WAN interface set to the first IP address in my block .145.  I set up virtual IPs for the other four addresses and the gateway was .150.

I'm reading around looking for the best way to set up the block of 5 IPs and dumb down the BGW320-505 as much as possible.  I'm also concerned that the tech or myself need to call and get my block of IPs moved over to my new router.  I'm assuming there's something they might have to provision that identifies my new router as me and moves things over.

In meantime, I've considered using passthrough and the dynamic IP to just get things working so our network isn't down.

I hope this helps, but I have a dedicated pfsense box that is used to doing static NATing / DMZ plus LAN / VLAN NATing.  I'm using some of the addresses for specific services while I reserve one of the addresses for my default NAT of IoT devices and such.  So I'm committed to keeping my block of IPs and getting things working with the new BGW320-505 gateway.

So the questions I have specifically are:
1. Do I have to use DHCP and change my interface configuration in PFSense to DHCP.  If so at the moment my Interface is static x.x.x.145/29.

2. Given my IP address range is x.x.x.145 - x.x.x.149 (/29) and gateway is x.x.x.150 what is expected in the cascading configution?

3. Do I need to call ATT to get my statics "assigned" to my new router or should it just work?


Thanks in advance.

Accepted Solution

Official Solution

ACE - Expert

 • 

35.8K Messages

2 years ago

The 5268AC doesn't have IP Passthrough, but it does have DMZplus, which is essentially the same thing.

The Public Subnet setup should be fairly straightforward if you are able to statically set the addresses on your devices.  If not, then you can allow them to be DHCP assigned and allocate them, but that's a messy process I don't recommend.

ACE - Expert

 • 

35.8K Messages

2 years ago

There is no reason to expect a gateway swap would cause any issue.  Swapping the Gateway should not change your public dynanmic IP address.  Your Public Static Subnet is routed to your Public Dynamic IP address, so it should still arrive there fine.  Your new Gateway may need to be programmed for the public static block (under Home Network > Subnets & DHCP in the Public Subnet section.  (I said "may" because AT&T attempts to copy some settings between a replaced router and the new router, e.g. SSID, Wi-Fi Passphrases and the like; it may also do the public subnet.  Even if it does, you may prefer to perform a factory reset on the new Gateway and populate all the settings by hand.)

I would strongly advise you not to mess with IP Passthrough with a Public Static Subnet on the same router.  If you wish to do so, you will be pretty much on your own.

(edited)

Tutor

 • 

49 Messages

2 years ago

Thanks for the quick response @JefferMC .  

Nothing transferred over as far as I can tell.  I still have my old modem and I turned it back on and logged into it (disconnected from AT&T) to see what the settings were on it.  It's been years since I went through the process of getting the 5268AC gateway to send all traffic to my PFSense interface and allow PFSense to do all the work.

So I can configure the Public subnet on the new gateway the BGW320-505, which seems similar to how it was done on the 5268AC.  The 5268AC doesn't technically have passthrough so it was all managed by setting IPs to static, turning firewalls off, and mapping source pings to Public network IPs.

I'm wondering if that will even work on the new gateway, and if so is it better for me to just set up cascading.  I remember (7 years ago) when I set up this up original switching from Comcast to AT&T Fiber that the 5268AC router was a (Edited per community guidelines) in comparison to how the statics worked with the gateway they had.  I was able to just let PFSense do all the work without having to do Virtual IPs, etc.


(edited)

Tutor

 • 

49 Messages

2 years ago

Thanks again for responding so quickly @JefferMC , especially on a US holiday.  I hope the day is treating you well.

Things are up and running again.  I set up the Public subnet, saved the configuration and PFSense pushed everything up and I'm back up and running as before.  No need for Pass-Through or Cascade configuration.  

Thanks for the help and I hope you enjoy the rest of your day.

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.