PACE 11.1.0.531418 DMZ Issue

You don’t owe anyone an apology. It is AT&T who owes every fiber customer an apology for stealing their money for over 3 months now.

Thanks so much for your kind words. To the end of ATT apologizing, please do whatever you can to document when the 11.1 firmware was pushed to your device, and call billing to insist on being compensated for every minute of service degradation you have suffered. For example, I was able to get the phone tech to confirm that they have evidence that my RG had 11.1 as of 1/30/19 at the latest. Support can't comp for service degradation - it has to come from billing so document all you can then contact them. Good luck all and thanks again!

I’ve been battling ATT regarding this issue for two months. I’ve likely spent hours on the phone with support and had multiple tech visits. Only recently has support agreed and confessed this issue exists with all Pace 5268’s on version 11. Unfortunately, support claims my account is locked into only receiving the 5268 or the NVG599. No one can explain why the BGW210 is unavailable for me. Perhaps it is because I am a Fiber customer only (no Uverse TV or phone)?

Regardless, like others here, I’ve received multiple 5268 replacements on firmware version 11 after being told the NVG599 would be shipped. Why do I continue wasting my time and money with ATT?

Short version of a long two months - wifi calling went haywire (I could hear fine but no one could hear me), days of troubleshooting and trips to electronics stores, and $400 spent on new routers before finally tracking the issue down to dmzplus and finding this thread. Serious *** AT&T.

I don't know if referencing this thread helped but it only took me about 5 mins on the support chat to get them to send someone that same day. Lucky for me he did have a BGW210 but said they are harder to get and sometimes they still issue 5268ACs. I wasn't about to go the shipping route after seeing so many folks here promised something else but receiving a replacement 5268.

BGW210 certainly seems zippier, both in the web ui and overall speed tests. The only negative so far is once turning on IP Passthrough I couldn't use 192.168.* for my local addresses. My Netgear R8000P complains that those addresses are reserved by the WAN subnet. Rather than battling it I just remapped everything locally to 10.0.0.* which wasn't fun but at this point I am tired of fooling with all this.

[word filter avoidance]

@signde 

Nicely done.

I'm surprised you had difficulty with the Netgear router.  I believe they are typically partial to using 192.168.0.x, at least that's what I remember.  Most routers allow you to choose the subnet range.  Generally I also like to manually control the WAN connection of the personal router and use manual setting of IP Passthrough on the Arris, but this is more a personal preference than anything else.

As many others, I rolled the dice with chat support and was sent the same model gateway.  I thought I might get lucky as they acknowledged the problem was with the gateway.  Having to schedule a truck roll now to hopefully get a different device.  For others with the issue I'd suggest going directly to a truck roll.

I figured there was some way to control the subnet but being so new to the BGW210 I just wanted all this working and changing my short list of local static IPs is something I'm familiar with. All my previous ASUS routers favored 192.168.1.x, which I would remap to 192.168.0.x. Upon plugging in the Netgear to either the previous 5268AC or the new BGW210, the Netgear prompts a message saying it's changed the local subnet to 10.0.0.x to prevent conflicts. This was before enabling dmzplus/ip passthrough. This my first Netgear after a decade of ASUS so wasn't sure if that's normal or not.

One thing that really threw me off figuring out the root cause - unlike my ASUS RT-AC86U which was just had 50/100 handicapped speeds, when the R8000P is put behind the 5268AC's dmzplus it would essentially become useless. All kinds of http timeouts just loading basic sites. I tried two different R8000Ps and both had same behavior, even after doing the power down reattach router modem song and dance. 

Well, unless you perform the offered workaround, I'm not sure I would bother using the 5268 with a personal router.

The benefit of using 192.168.0.x. subnet with appropriate mask will allow access to the management console from the clients on the personal router.  And I totally get the issues around managing home network.  It's tough to get used to one router let alone 2, 3, or more.

Maybe I'm confused about this issue. I thought it was only an issue with the 11.1.0.531418 firmware and the older firmware worked fine. It's my understanding that you can just flash an older version to resolve the problem. Also, I've seen reports that ATT is no longer pushing the latest firmware so the older version will "stick" and not be upgraded. Am I mistaken?

That sounds right, but test and verify for yourself.