I’ve tried upgrading from 8.4.1 to 8.5.0 on two occasions. For the most part, the network has worked fine, however, the WAN quality monitoring on one of my 3 connections doesn’t ping the right address. It pings a local IP address rather than something on the public internet.
I’ve uploaded two screenshots, one is from the first time that I reverted back from 8.5.0 to 8.4.1, and you can see this WAN connection quality monitoring started working again with pings in the 20 to 40 ms range. The second screenshot shows the second time that I tried upgrading from 8.4.1 back up to 8.5.0, and you can see the same WAN connection quality monitoring goes from the 20 to 40 ms range down to 4 to 6 ms, which is the same latency I get when I ping the WAN router from one of the LAN devices. I see the same results whether I look at the quality monitoring from the local device admin vs. InControl2.
This makes the WAN quality monitoring for that connection kind of worthless, since it isn’t showing the quality of the connection out to the internet, rather the quality of the connection from the Peplink router to the 5G cellular modem.
I’ve filed a ticket with Peplink support, who claimed that the WAN Quality Monitoring tries to use traceroute first, and then if that fails, it falls back to using ping. Support claims that on this connection under 8.4.1, the traceroute was failing so the router instead was using ping (which provided correct/relevant results). Peplink support asserts that under 8.5.0, the traceroute is “succeeding” so that is the result that is returned, and that this is not a bug, but rather a request for improvement in a future version.
How is WAN Quality Monitoring “succeeding” if it is simply monitoring the connection to the router? That’s not the WAN?!
I have two MoCa adapters between the cellular modem and the Peplink B One on that specific WAN connection, and I’m guessing that perhaps the traceroute is getting thrown off by them. Any recommendations on what IP / subnet to set those to in order to prevent this? Or perhaps there are specific DNS settings I can use for that WAN connection as a workaround?