@MD83 I'm assuming that Rogers is using that 45.xxx.xxx.xxx block internally, which is a little odd, but, it is what it is.
Just to see whats up, and not worry about any confusion with the modem or TP-Link configuration, try pinging Rogers primary IPV4 DNS: 220.127.116.11
I'd let that run in the background while you're running the normal household internet activities. That might cause higher latency, but, I suspect the family would revolt if you said, "no internet for an hour!" Ok, so, run:
ping -n 3600 18.104.22.168
Lets see how that turns out.
@wsxedc so that's a consequence of running google wifi, it takes over your trace routes?
I couldn't discount the format as I'm by no means aware of all of the trace commands and results available to Rogers customers. Maybe in a few more years 🙂
Sorry, I was getting that from phone and its selected all with copy. There is latest from laptop along with trace route from google. Please analyze and let me know as I have a tech visit tommorow and would like some insight before.
Oh yeah coda 4582 fw ver
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||22100000||ATDMA - 64QAM||33.250||1||3200000|
|2||36996000||ATDMA - 64QAM||28.000||4||6400000|
|3||30596000||ATDMA - 64QAM||30.000||3||6400000|
|4||25300000||ATDMA - 64QAM||34.500||2||3200000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
Ping statistics for 22.214.171.124:
Packets: Sent = 3600, Received = 3537, Lost = 63 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 3434ms, Average = 28ms
@savuser12 your DOCSIS 3.0 channels (1 to 32) are higher than they should be, arguably within spec, yes, but, then should be down around 0 dBmV. Your QAM levels are ok, the signal to noise ratios are ok as well.
The upstream DOCSIS 3.0 levels aren't too bad where they currently sit.
The DOCSIS 3.1 OFDM channel can't be assessed as the signal level, signal to noise ratio and QAM Level isn't presented to the user. Tech support has access to that data, and I would expect the field techs to have access to that data as well.
My personal opinion about the packet loss in the ping test is that its higher than it should be, but, I base that on my test results from West Ottawa, which are typically well under 1%. The distribution of the high ping times (latency) would be interesting to see and it might be the more important point here. That's something I have to work on to make it easy to accomplish.
On the surface, yes the downstream signal levels are higher than normal, but, given the problems with the Rogers network these days, you might not have any problems caused by local issues. That's really problematic these days, are the problems local, or are they network issues? Really the only thing the tech can do is check the cables and connectors for continuity. That's a minor check and might not do much if anything to address any latency and packet loss that you're seeing 😞