This was based using a Pace 5258AC gateway, but I retained the same setup when I setup the bypass using an Edgerouter. I am not 100% sure if this is YOUR issue, but I do know that with any of the gateways, things re: firewalling/port forwarding etc runs a lot smoother if you leave the entire 192.168.1.0/24 network exclusively to the gateway itself, and just pick any other /24 within the private address space for your home network.

I went for 192.168.2.0/24, as it was the easiest to just change the 5 or 6 static IP's I have configured from a '1' to a '2' on the third IP digit. The solution though is deceptively simple: If you run your own network on a subnet other than 192.168.1.0/24, it works just fine. The reason for this is because the gateway exists on 192.168.1.254, and the default network for the clients is also in the same /24 address space, and in some cases it gets confused if it needs to forward a port within the same /24 as the gateway itself.

There are some known issues with port forwarding on ports that AT&T themselves also may use for remote management such as port 443 and 22.

At t uverse open ports