Based on my experience of having run in a double NAT for the better part of eight years no it should not cause any packet loss.
Are you using any port forwards or DMZ settings?
What router are you using as your internet facing router? I suppose it if doesn't have adequate processor speed it might not be able to keep up with your GT-AC2900 on a 500/20 connection. If you connect directly to your first router with a PC do you get your full 500/20 speeds?
Also you could disable Diversion as a test and see if that might have an impact on packet loss.
It went away when I took the screenshot, but when I first started it, the Asus Router was at 40 percent packet loss and the ISP Gateway was at 20 percent packet loss.What packet loss on the ISP gateway? None is shown in your screenshot. The only packet loss is to your GT-AC2900.
Once you get your packet loss issue fixed take you ASUS router out of the DMZ as this isn't necessary to get a double NAT to function unless you are running some type of server on your ASUS and are doing this instead of a double Port forward.Yes in my ISP Gateway (XB6) it supports gigabit speeds, I have my 2nd router in DMZ mode so that all the ports are open to it.
Unable to do that manually on the gateway. ISP doesn't allow it, and we have way too many devices to attempt to go through the hassle of changing every single DNS server.maybe set cloudflare or google as your dns server ? 188.8.131.52 or 184.108.40.206 (corrected)
Fixed itself. Thanks.Once you get your packet loss issue fixed take you ASUS router out of the DMZ as this isn't necessary to get a double NAT to function unless you are running some type of server on your ASUS and are doing this instead of a double Port forward.
Also just for grins since you are already running diversion add Skynet and see how many hits you are taking daily from the "bad guys". It will be a lot since your router is in the DMZ.
Thanks for this.Yes if you turn DMZ your first router would provide most of the firewall protection but with Skynet you have additional options which makes it possible to selectively block more IPs and ranges of IPs. I block countries that I see knocking often in Skynet. I have never run Skynet on a router double NATed behind another so I don't know how it will work if you disable DMZ.
Yep, was already doing that.You can get false packet loss indications from Pingplotter. Thats yet another problem with using Pingplotter. So, if you do this in stages:
1. Ping the router (just the router) via ethernet, you should not see packet loss. This should convince you that there's no packet loss to or from the router.
2. Ping the modem. You might see packet loss from the router where you have just proved to yourself that the router has not packet loss. In this case, you shouldn't see packet loss from the modem.
3. Ping the CMTS (just the CMTS) which is hop #3 on the route to anywhere. You might see packet loss from the router and modem where you just convinced yourself that both router and modem don't suffer from packet loss. Note that in your case the modem shows up in the pingplotter trace due to the fact that its running in Gateway mode.
Fwiw, false packet loss indications from Pingplotter are a problem with the Hitron CODA-4582 which is an Intel Puma 7 modem.
If you do end up with packet loss indications with Pingplotter, you need to confirm that with a ping test using the windows Ping command or other command line application.
Also fwiw, you should see a response time at or under 1 milli-second from the modem. I wouldn't expect to see any large latency spikes from the modem, unless of course the modem is busy doing something that preempts the low priority ping response.
Yep, and I know that a CCTS complaint costs them money, which is why I don't want to do that right away.Yup, I'm on the Rogers forum as well.
I'd definitely follow this up with the Office of the President. This is really simple. Tell the customers what the loads are on the neighbourhood nodes and CMTS when there are problems such as this. That load number will indicate whether or not its time to split the node. Splitting the node isn't an instantaneous action. It usually takes weeks to plan out and put into action, but, its a simple task to review the load numbers and give the customers an honest reply instead of forcing the customers to complain time and time again, followed by a CCTS complaint. Its a self inflicted wound for Rogers that starts when a customer calls tech support for the first time, only to be told that nope, there's nothing wrong here