10-30-2018 9:12 PM
I put my router behind the PACE gateway and set the router as DMZ. The latest firmware is crapping out my fiber connection where I'm only able to get 50mbps down and 1-200 up. I thought it was my router crapping out, but apparently when I connect any other device directly to the gateway, I'm able to pull 940mbps up and down. I swapped an older router and placed that device in the DMZ And it starts acting up and the previous router started working normally.
Can someone look into this?
Solved by: Go to Solution.
11-02-2018 7:55 AM
discovered the same issue this morning. No matter what device gets assigned the wan IP passthru/DMZ setting, that device and anything behind it are slow. Can reproduce it on a laptop, on a physical Unifi firewall, and on a PFSense VM. I'm assuming the firmware version 188.8.131.521418-att must be Nov 1st. Thanks for screwing the pooch AT&T.
11-02-2018 10:34 AM
Lol my solution was to hit up AT&T support and they swapped me into a NVG599 gateway. This one works better and is less sluggish navigating pages in the config interface.
11-02-2018 7:19 PM
I just got off the phone with ATT support. After spending about 15 minutes with them going through their troubleshooting process, they are sending me a new modem. It will deliver Monday. I was honestly surprised since they had me direct wire to the modem from my PC and the speeds were normal. I told them that is what I expected and that the issue is when I am using my router. He put me on hold about 1 minute, came back and said I needed a different modem.
11-02-2018 8:58 PM
Changing modems won't fix your problem, if you have the DMZ issue I mentioned. Any devices put into the DMZ will get sluggish speeds around 50mbps down and 200ish up. It's something to do with the recent firmware. Unless you get a different model modem like I did (NVG599), which IMO works better than the PACE.
- edited 11-09-2018 10:54 AM
So glad I found this thread. I have spent days trying to figure out what the heck is going on. In my case, I first noticed that my WI-FI calling via AT&T Mobility had started to have issues. Mainly UL voice was getting clobbered. Then it got worse and worse where I started to miss calls. Then I heard others that started to have issues, so I started to troubleshoot.
First, let me point out that I use a Ubiquiti USG router and Ubiquiti UNIFI AP, as I prefer to use my own, and also like the performance of UBNT equipment. . I did speedtests, all seemed to be ok. But WIFI calling is all messed up and I also get occasional odd delays. I did try a SKYPE business call and it was ok though. Not sure if perhaps a different port is used? I assume both would be UDP?
So on to my troubleshooting. One thing I noticed was that each time I clicked on firewall > firewall rules, I never got anywhere and the phone call I was on (VOIP port on RG) would mute for about 10 seconds. I was able to repeat this over and over. I could never get to the webpage to edit firewall rules. So this is when I decided it was time to factory default the RG. After it came up, bingo! WIFI calling worked just fine and all was good, at least at first. Note that I had not yet placed my own USG router into DMZ mode yet. So I continued with my provisioning of the 5286 to put my USG router into DMZ mode, and told my USG to grab the public IP and that’s when all went down hill again. Also, after setting DMZ mode, you can’t go into firewall > firewall rules anymore, and the routers really goes nuts after that. Definitely a bug!
I then googled 184.108.40.2061418-att and found this thread. There is something definitely wrong with this version. Even if you don’t use DMZ plus mode, there seems to be issues though, I know a few with the 5286 that also complained of not being able to get WIFI calling to work correctly. It just seems to get worse when you use DMZ plus mode, and for some of you it has even more performance issues if you are fiber. I am still copper to the node, so I am capped at 48 mbps, but this is a huge issue for me. If I use the router’s wifi, then it seems to be ok from what I can tell. I hope someone from AT&T is seeing this. I will also try to reach out to folks to bring attention to this. I just learned that the NV599 is a good one. So I am going for that as the replacement and heard that this is the one to get. Comments?
11-09-2018 6:41 AM
Same issue. Factory reset the modem. I tested with 3 different devices, different cables, on different ports. Any device set as DMZ gets about 60/170 Mbps. The rest work fine.
I just called AT&T support and ordered an NVG599. Let's hope this fixes the issue. These Pace 5268 modems have the worst firmware ever. That "secret" 5GHz wireless network was a pet peeve of mine, I'll be glad to be rid of it.
11-09-2018 6:43 AM
I have confirmed. They are sending out NV599 if you call in. Just explain you are impacted with the latest firmware and they will send out a NV599. You have to return the old one to a UPS store.
11-09-2018 6:59 AM
Below was my experience - It's right now, but it was a hassle
1. I had this issue. Called ATT support, they said they would ship me a BGW-210
2. They sent a NVG-599 which also had some issues with it. Called again and they assured me they would send a BGW-210.
3. They sent an NVG-589 this time. Called support again, and the advanced support guy literally chuckled and said that the only way I would for sure receive a 210 would be to have a tech come out to my house.
4. Next day, tech arrived and swapped me over to a BGW 210.
Visit these related resourcesView New Device Help!