Router Behind a Uverse/Pace 5268ac Gateway Loses its Mind Every 10 Minutes

Router Behind a Uverse/Pace 5268ac Gateway Loses its Mind Every 10 Minutes

Late last year, I had my AT&T Uverse residential gateway replaced.
For reasons that truly baffle me, AT&T has decided that
they are going to run unsupported equipment on their residential customer network
.
When the replacement was swapped in, my family noticed that video conference calls—Zoom and Facetime and Slack—would occasionally drop out for about 10 seconds before continuing.
After much frustration, I started timing the outages and found that they were happening at roughly 10-minute intervals (plus or minus just a few seconds).
Some internet searching lead to a forum post (
page 1
,
page 2
) on AT&T’s customer site.
As it turns out, there is a conflict with the DHCP address assignment messages when the residential gateway is in DMZplus mode.
1
Forum user «weshunt» had the right solution:
I’m not a network confguration expert, but it bothered me that the Pace [residential gateway] and the USG both wanted to use 192.168.1.x for DHCP allocations. I noticed that even after putting the USG into the DMZPlus, I could connect a wireless device and it would get an address in the Pace’s default 192.168.1.x range, which conflicted with the IP range the USG was trying to manage. And of course the Pace answered to 192.168.1.254, which was also in the default allocation range of the USG.
So I changed the DHCP settings on the Pace to answer to a different subnet (192.168.100.1 with a DHCP allocation range inside 192.168.100.x as well). Like magic, the USG immediately picked up the DHCP assignment from the Pace and got the public IP exactly like I wanted. Now the networks don’t seem to want to fight each other. I can still access the Pace from the wired network via the new gateway IP (192.168.100.1), and also connect to the Pace wirelessly using the old SSID if I need to, though I’m shutting that down to alleviate unnecessary wireless congestion.
Step by step, this is what you need to do.
Change the LAN DHCP Range
With a web browser, go to your residential gateway advanced device configuration page.
The link for this will be printed on the bottom of the gateway and is probably http://192.168.1.254.
You will also need the «Device Access Code» that is printed just below that web address.
I’m using a hardwired ethernet connection between my desktop and the residential gateway, but this will probably also work over wireless, too.
Click on
Settings
… then
LAN
… … then
DHCP
.
In the «DHCP Configuration»→»DHCP Network Range» section, select «Configure manually» and enter these values:
Router Address: 192.168.100.1
Subnet Mask: 255.255.255.0
First DHCP Address: 192.168.100.100
Last DHCP Address: 192.168.100.200
DHCP Lease Time: 24
At the bottom, click «Save». You’ll need your Device Access Code at this point to save your changes.
Pace Residential Gateway DHCP Configuration Page
The IP address ranges on the LAN side of the residential gateway have now changed, so t…