PACE 11.1.0.531418 DMZ Issue

Well, I just plugged the new one in (power only) and it has 11.1.0.531418-att on there, just like my current one.  So, unless they get downgraded after connecting to AT&T's network, this one is equally useless.  Thanks for the info!

@healthy_scratch You may already be aware but you can force the downgrade yourself. I think the only downside to that is a very slow GUI and maybe an issue with WIFI not disabling. 

@healthy_scratch I've been using my replacement 5268AC for over a month.  It came with 10.x firmware and hasn't been upgraded yet - fingers crossed. 🙂

After a somewhat-frustrating 15 minute call with support, I have a tech coming and the ticket has a note that I need an RG that is NOT a Pace 5268AC. Or it's possible that the note states: "Bring another Pace 5268AC for this guy's collection and ensure that it has 11.1!"  I'm afraid some key words might have gotten lost in translation during that call... In hindsight, I should have just said, "The Internet doesn't work at all!  I need help!  Please send a tech to come fix it right away!" and never mentioned confusing things like "DMZ plus" or "Pace 5268."

As far as the forced-downgrade, I have the 10.7 firmware sitting here, but would prefer to avoid that.  I don't want any issues down the road.  Plus, I loathe going into the RG setup when it's running normally (slow)... the thought of having it painfully slow is even worse.  If I can't get a solution working after the visit, I'll try downgrading one of these 5268 units.

Since this thread is marked Solved (and it's not solved), perhaps a new one is in order?

I've been running downgraded firmware for weeks and it hasn't been updated.  I don't think that they are currently rolling out updates because of these issues.  I initially downgraded to 10.5 before finding this thread.  My speeds returned (940/950), but I was having some intermittent stability issues with the connection.  I upgraded to 10.7 and now I'm having issues with the pace wifi.  The 5ghz won't disable and the 2.4ghz just doesn't seem to work.  I get "ERROR" when I try to save wifi settings.

The wifi issues aren't a huge problem.  Previously I had my IOT devices using the PACE wifi to isolate them from my internal network.  Now I created a guest network on my Asus router for them.

The biggest problem right now is that the disgustingly slow response from the web interface (literally have to wait 10 minutes for a response after clicking something) makes it very difficult to troubleshoot issue like the wifi on 10.7 or the stability on 10.5.

I downgraded back to 10.5 and everything seems to be good.  Wifi is working correctly.  The web interface is MUCH faster, but still a little laggy.  Some times it takes a minute to respond vs the 10 minutes on 10.7.I don't have the link to the 10.5 download anymore.  I found it in another thread on these forums.  The file for it is 5268.install.pkgstream.

The speed test that I just took while my two kids are streaming youtube and my wife is streaming Netflix resulted in 0ms ping, 927.89 down, 930.47 up.

Situation update: I got a service call on Sunday.  As usual, the tech was friendly and helpful.  He brought a BGW210-700 and DMZ+ was working at full speed (~940Mbps up and down at 2ms ping) about 10 minutes later.  The tech mentioned that they like the Pace simply because it has the coax option (and everyone has coax running all over their house).  Perhaps that's why everyone always gets a 5268 over the phone?  Who knows.

Anyway, so far so good on the BGW210!

That would only matter if the subscriber has Uverse TV.  And frankly if the option to not use Coax is there even for an IPTV user, they should take it.  Unless you know the actual business rule implemented in their ordering system, no sense speculating.  The results speak for themselves.  People who read this thread can either heed the advice given or take the long way to an eventual conclusion.

This is absolutely crazy that this has been going on since November and no solution. The item marked as a solution is really a work around that doesn't solve the issue. How in the world has ATT not updated the firmware to solve this? It appears if you use your own router behind the PACE 5268AC on the 11.1.0.531418 firmware you're going to have this problem. How in the world has ATT not solved this? It's nearly February?