Posted: Sat Nov 17, 2018 18:45 Post subject: Sudden Loss of Bandwidth on DLink DIR-890
My DLink DIR-890 router has been running flawlessly after having updated to the latest firmware 5 months ago. It is sitting behind AT&T’s Pace 5268AC serving up their 1GB fiber service. I routinely got 800-900MB down on a hardwired PC downstream from the DIR-890, until a few days ago. Now, I’m barely getting 40mb down. This speed was also verified from the ATT gateway’s built-in speed test, so I suspected the issue was with the ATT equipment.
ATT said they showed errors on the line and sent out a tech, who replaced the fiber ONT, which restored their gateway speedtest to correct levels. The tech tested out and verified proper speeds immediately inside on their gateway ports, so it would appear their stuff is good. Yet speeds from the dd-wrt built in test still shows 40mb, and verified from a hard wired PC.
What could have gone belly up? DIR-890 firmware is DD-WRT v3.0-r36168 std (06/20/1.
Not looking forward to ripping out my wiring closet to troubleshoot, but is there somewhere in the configurations that I could review first?
Everything I’m testing is hardwired - no Wi-Fi involved.
So, can I go from a current beta version (is it brainslayer that’s downloaded here?) right into a Kong firmware? I looked into Kong’s some time ago before SFE was available, but loading it wasn’t overly apparent.
But my question stays the same: what would cause a solid, working dd-wrt install suddenly go into the tank? Since I haven’t messed with configurations for some time other than an occasional reboot, it seems like there would have to be some external interaction causing this. I do use a ddns service, and use OpenVPN to allow remote access into my network, and have a few ports forwarded. Grasping at straws, here.
I erased nvram after loading dd-wrt, then restored from a backup (taken when the router was working at full speed).
Knowing that factory firmware works, I hate to go to the expense of replacing the router only to end up with the same results, but may need to try. To have something that was working suddenly degrade like this still makes me think there’s a hardware issue.
The only other things in the setup that I can think of would be:
- erasing nvram isn’t fully doing its job.
- an auto firmware update to the AT&T modem that has something obscure that dd-wrt doesn’t like.
I use the Velop mesh network gear for Wi-Fi and so have that portion of my router turned off. Is there a good gigabit router suitable for dd-wrt that does not have Wi-Fi capability?
Didn't really matter in this case, egc. Further up, I mentioned that speedtest reflected the same poor speeds right after applying the factory-to-ddwrt.bin file from DLink stock, even before applying any settings or restores.
Dunno... Something has just gone belly-up for no apparent reason, after at least 5 months of solid performance. Doesn't make sense, and I'm at a loss on what else to try at this point.
I may have touched on the issue earlier - I stumbled on a rash of recent posts online that exactly mimics my situation. It appears that sometime in October, AT&T issued a firmware update to their 5268ac that has messed with DMZ Plus mode, effectively capping folk’s bandwidth to around 50mb. After having operated fine for a period of time, people started experiencing this issue with no change to their setup.
True to form, AT&T is not addressing the issue, and their tech support is blaming it on everyone’s router.
In DMZ Plus mode, I used to give my router/internal network a different IP scheme than that of the gateway’s default IP. So, not being a firewall guy, if I remove my router from DMZ Plus, how could I create a hole in the AT&T gateway for all ports and services without getting into a double NAT situation?
I think they have other hardware that uses IP pass through instead of DMZ Plus. Would that be a better option if I could get them to swap It out?