Question about Signal Levels

Need Help?

That's what we're here for! The goal of the Rogers Community is to help you find answers on everything Rogers. Can't find what you're looking for? Just ask!
cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
I Plan to Stick Around
Posts: 8

Re: Question about Signal Levels

@Gdkitty & @Datalink & @gp-se   

 

Besides game lagging reported by my 10 yr old, I have a VOIP service that goes down almost daily, when port 5060 gets locked and my PAPT2 fails to register. 

 

So in anticipation of tomorrow's Tier II tech visit, I ran some stats (as seen from Brutal-latency-ping-Recently).  Besides asking him to reduce the downstream signal closer to 0dB - is there anything, you see, I ought to bring to his attention? 

 

Tracing route to www.google.com [172.217.164.228] over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 18 ms 10 ms 10 ms 99.234.60.1
3 12 ms 9 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 16 ms 9 ms 10 ms 209.148.235.73
5 13 ms 20 ms 10 ms 209.148.233.38
6 * * * Request timed out.
7 14 ms 19 ms 13 ms 74.125.244.161
8 11 ms 11 ms 9 ms 216.239.42.619 18 ms 14 ms 9 ms yyz12s05-in-f4.1e100.net [172.217.164.228]

Trace complete.

 

1.  Ping statistics for 99.234.60.1:
Packets: Sent = 3600, Received = 3589, Lost = 11 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 317ms, Average = 16ms

 

2.  Ping statistics for 64.71.255.204:
Packets: Sent = 3440, Received = 2528, Lost = 912 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 509ms, Average = 11ms

 

3.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| hitronhub.home - 100 | 264 | 1 | 1 | 1 | 1 | 1 |
| 99.234.60.1 - 1 | 1275 | 1265 | 6 | 15 | 182 | 13 |
| gw01.ajax.phub.net.cable.rogers.com - 1 | 1283 | 1275 | 3 | 13 | 244 | 9 |
| 209.148.235.57 - 1 | 1287 | 1280 | 5 | 14 | 110 | 15 |
| 209.148.235.42 - 1 | 1299 | 1295 | 8 | 16 | 383 | 15 |
| 72.14.222.87 - 1 | 1283 | 1275 | 6 | 15 | 174 | 10 |
| 108.170.250.241 - 1 | 1298 | 1294 | 6 | 14 | 106 | 12 |
| 216.239.35.233 - 1 | 1306 | 1304 | 6 | 15 | 511 | 13 |
| dns.google - 1 | 1295 | 1290 | 5 | 13 | 246 | 10 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Question about Signal Levels

@JSS_BRAMPTON how's that for service.  Wish I could take credit for that, lol 🙂

 

Ok, as @Gdkitty indicated, your signal levels are still high, so yes, they could drop by another 3 dB.  However, looking at the signal levels it would appear that there's a noise issue on the cable line that runs from the neighbourhood node to your local tap.  My guess is that the noise source is fairly close to your home, unless its putting out enough noise that its affecting the entire line to a very large extent.  If you look at the before and after results, you can see the drop in signal to noise ratio in the upper DOCSIS 3.0 channels (1 to 32).   For a 6 dB drop in signal level, you also dropped about 6 db in signal to noise ratio.  

 

Personally I wouldn't want the signal to noise ratio to drop any further, so I'd hold off on any further signal drop by installing a 9 dB attenuator.  I think you'll run into problems due to the signal to noise ratio if you drop the signal level any further.  

 

I think at the present time you should have a chat with tech support to determine if the senior tech raised a ticket last night for another senior tech or maintenance crew to look at the noise levels in your neighbourhood.  Following that the conversation can take one of two directions, one, there is another senior tech or maintenance crew already assigned to a ticket to track down the noise, or two, the Customer Service Rep looks at the noise level up and down the line and raises a ticket to do the same.  I think that should be the first step before another tech arrives to swap the attenuators.  If so, then tomorrow's tech should be postponed for now. 

 

If you have a chat with tech support please let us know how it went.  

 

Edit:  looking at your ping test results, the test to the DNS is pretty ugly.  Can you run a short test, 50 pings and post the results, just to see what it looks like when its running?  Run:

 

ping -n 50 64.71.255.204

 

Please post that entire test, from start to finish when its done.  



Highlighted
I Plan to Stick Around
Posts: 8

Re: Question about Signal Levels

@Datalink  Hi... Sorry I guess I was still editing my post when you responded.

Here is the test ping -n 50 64.71.255.204 requested by yourself:

 

Pinging 64.71.255.204 with 32 bytes of data:
Reply from 64.71.255.204: bytes=32 time=94ms TTL=58
Reply from 64.71.255.204: bytes=32 time=21ms TTL=58
Request timed out.
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=31ms TTL=58
Reply from 64.71.255.204: bytes=32 time=11ms TTL=58
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=30ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=39ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Reply from 64.71.255.204: bytes=32 time=20ms TTL=58
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=18ms TTL=58
Reply from 64.71.255.204: bytes=32 time=44ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Request timed out.
Request timed out.
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=34ms TTL=58
Reply from 64.71.255.204: bytes=32 time=51ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=16ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=19ms TTL=58
Reply from 64.71.255.204: bytes=32 time=15ms TTL=58
Reply from 64.71.255.204: bytes=32 time=32ms TTL=58
Request timed out.
Reply from 64.71.255.204: bytes=32 time=28ms TTL=58
Reply from 64.71.255.204: bytes=32 time=13ms TTL=58
Reply from 64.71.255.204: bytes=32 time=12ms TTL=58
Request timed out.
Request timed out.

Ping statistics for 64.71.255.204:
Packets: Sent = 50, Received = 34, Lost = 16 (32% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 94ms, Average = 22ms

Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Question about Signal Levels

@JSS_BRAMPTON here's an experiment I'd like you to try if you have the time and patience.  If so I'd like you to run two command prompts simultaneously.  To do that start one command prompt and then simply hold down the shift key and select the command prompt again to start the second instance.  

 

1.  For the first command prompt, run a ping test to the DNS:  ping -t 64.71.255.204

     Start that test and just let it run.  To terminate it at some point use Ctrl +c

 

2.  For the second command prompt, type in a trace command to the DNS but, don't fire that until you see a "Request timed out."  The instant you see the time out, hit enter to start the trace.  What I'm hoping is that you'll start the trace during a series of time outs, two or three timeouts in a row.  I'd like to see what that looks like, if you can manage to pull that off.  Looking at the ping results, its looks like you don't have to wait very long before a series of time outs occur.  Its a bit of a guessing game when you trigger the trace, you won't know if you've hit the right multiple time out sequence until the trace is actually running and you see any additional time outs occur.  To quickly reenter the trace command when its done, hit the arrow up key when your curser is in the second command box to return to the previously entered command.  If you were using a series of commands, you can arrow up or down throughout the commands to reuse previously entered commands.  In this case, arrow up and simply wait for the next "Request timed out." to occur and hit enter to rerun the trace.  

 

How does that movie opening go "Your mission if you choose to accept it"......  Something like that.

 

Time and patience permitting, if possible:)  Hopefully it might produce something that @RogersAndy or @RogersTony  can use to forward to the engineers.  No guarantees but, worth a look to see what it produces.

 

Also when you have time, can you run the following IPV6 trace and ping to the primary IPV6 DNS:

 

tracert 2607:f798:18:10:0:640:7125:5204

 

ping -n 50 2607:f798:18:10:0:640:7125:5204

 

Please post those results as well.  To post the trace, please copy the trace results, paste them into a text editor and wipe out the entire portion of the hop #1 address to the right of the 2607 portion of the prefix.  That hop #1 address is the modem's address which shouldn't be posted in an open forum.  After wiping out most of that address please post the results.   



Highlighted
I Plan to Stick Around
Posts: 8

Re: Question about Signal Levels

@Datalink Mission accepted - ran several trace routes, trying to sync requests to time outs seen; for some reason IPV6 trace and ping to the primary IPV6 DNS failed.  Hope this sheds some light as to what's going on here. 

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 16 ms 17 ms 10 ms 99.234.60.1
3 8 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 7 ms 8 ms 209.148.232.229
5 8 ms 11 ms 8 ms 209.148.227.157
6 12 ms * 10 ms 10.202.47.161
7 9 ms * * dns.cp.net.rogers.com [64.71.255.204]
8 * * 10 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.


tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 15 ms 99.234.60.1
3 11 ms 9 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 12 ms 9 ms 209.148.232.229
5 11 ms 8 ms 9 ms 209.148.227.157
6 * 10 ms * 10.202.47.161
7 * 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 2 ms hitronhub.home [192.168.0.1]
2 48 ms 9 ms 10 ms 99.234.60.1
3 7 ms 7 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 9 ms 9 ms 209.148.232.229
5 11 ms 8 ms 8 ms 209.148.227.157
6 22 ms 10 ms 9 ms 10.202.47.161
7 * 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 48 ms 10 ms 7 ms 99.234.60.1
3 9 ms 10 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 8 ms 209.148.232.229
5 9 ms 10 ms 9 ms 209.148.227.157
6 10 ms 10 ms * 10.202.47.161
7 10 ms 12 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 10 ms 99.234.60.1
3 9 ms 4 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 14 ms 209.148.232.229
5 10 ms 9 ms 10 ms 209.148.227.157
6 18 ms 13 ms 7 ms 10.202.47.161
7 * 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 29 ms 10 ms 10 ms 99.234.60.1
3 9 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 9 ms 209.148.232.229
5 9 ms 12 ms 10 ms 209.148.227.157
6 15 ms 9 ms 10 ms 10.202.47.161
7 9 ms * 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 11 ms 10 ms 9 ms 99.234.60.1
3 9 ms 8 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 8 ms 9 ms 10 ms 209.148.232.229
5 8 ms 10 ms 7 ms 209.148.227.157
6 13 ms 9 ms 10 ms 10.202.47.161
7 10 ms 11 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 7 ms 9 ms 10 ms 99.234.60.1
3 11 ms 7 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 15 ms 9 ms 8 ms 209.148.232.229
5 10 ms 10 ms 12 ms 209.148.227.157
6 10 ms 31 ms 16 ms 10.202.47.161
7 9 ms * * dns.cp.net.rogers.com [64.71.255.204]
8 11 ms 9 ms * dns.cp.net.rogers.com [64.71.255.204]
9 * * * Request timed out.
10 * 8 ms 11 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 14 ms 10 ms 99.234.60.1
3 7 ms 7 ms 6 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 11 ms 9 ms 8 ms 209.148.227.157
6 14 ms 10 ms * 10.202.47.161
7 9 ms 7 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms * <1 ms hitronhub.home [192.168.0.1]
2 10 ms 8 ms 10 ms 99.234.60.1
3 9 ms 9 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 8 ms 209.148.232.229
5 9 ms 10 ms 10 ms 209.148.227.157
6 * * 9 ms 10.202.47.161
7 10 ms 9 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 17 ms 99.234.60.1
3 9 ms 11 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 9 ms 10 ms 209.148.232.229
5 15 ms 11 ms 10 ms 209.148.227.157
6 9 ms 8 ms 10 ms 10.202.47.161
7 9 ms 6 ms 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 9 ms 99.234.60.1
3 9 ms 10 ms 11 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 13 ms 9 ms 209.148.232.229
5 11 ms 7 ms 8 ms 209.148.227.157
6 10 ms * 9 ms 10.202.47.161
7 * 8 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 11 ms 8 ms 10 ms 99.234.60.1
3 8 ms 8 ms 10 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 13 ms 11 ms 10 ms 209.148.232.229
5 9 ms 16 ms 9 ms 209.148.227.157
6 65 ms * 8 ms 10.202.47.161
7 10 ms 9 ms 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * <1 ms 1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 11 ms 99.234.60.1
3 9 ms 8 ms 11 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 17 ms 11 ms 24 ms 209.148.232.229
5 14 ms 9 ms 7 ms 209.148.227.157
6 10 ms * 11 ms 10.202.47.161
7 11 ms 8 ms * dns.cp.net.rogers.com [64.71.255.204]
8 8 ms 7 ms 19 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms hitronhub.home [192.168.0.1]
2 9 ms 9 ms 9 ms 99.234.60.1
3 11 ms 10 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 508 ms 7 ms 9 ms 209.148.227.157
6 10 ms * 9 ms 10.202.47.161
7 * 11 ms 19 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 9 ms 99.234.60.1
3 10 ms 9 ms 7 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 12 ms 11 ms 209.148.232.229
5 10 ms 8 ms 11 ms 209.148.227.157
6 * 12 ms 9 ms 10.202.47.161
7 * 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 10 ms 10 ms 99.234.60.1
3 8 ms 8 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 10 ms 9 ms 10 ms 209.148.232.229
5 10 ms 10 ms 8 ms 209.148.227.157
6 11 ms 12 ms 8 ms 10.202.47.161
7 13 ms * 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 10 ms 16 ms 99.234.60.1
3 10 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 10 ms 10 ms 209.148.232.229
5 10 ms 10 ms 10 ms 209.148.227.157
6 * * * Request timed out.
7 * 9 ms 10 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 8 ms 13 ms 8 ms 99.234.60.1
3 11 ms 8 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 10 ms 10 ms 209.148.232.229
5 9 ms 8 ms 11 ms 209.148.227.157
6 14 ms 14 ms 10 ms 10.202.47.161
7 * 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 6 ms 10 ms 99.234.60.1
3 9 ms 15 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 11 ms 10 ms 209.148.232.229
5 9 ms 10 ms 10 ms 209.148.227.157
6 9 ms 8 ms * 10.202.47.161
7 7 ms 8 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 8 ms 8 ms 7 ms 99.234.60.1
3 11 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 10 ms 9 ms 209.148.232.229
5 8 ms 9 ms 8 ms 209.148.227.157
6 * 15 ms 9 ms 10.202.47.161
7 7 ms * 7 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 9 ms 8 ms 9 ms 99.234.60.1
3 8 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 9 ms 9 ms 209.148.232.229
5 10 ms 9 ms 9 ms 209.148.227.157
6 17 ms 17 ms 9 ms 10.202.47.161
7 * 64 ms * dns.cp.net.rogers.com [64.71.255.204]
8 9 ms 9 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms hitronhub.home [192.168.0.1]
2 10 ms 61 ms 49 ms 99.234.60.1
3 9 ms 7 ms 16 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 11 ms 13 ms 9 ms 209.148.232.229
5 9 ms 9 ms 9 ms 209.148.227.157
6 9 ms 12 ms 9 ms 10.202.47.161
7 8 ms 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 12 ms 12 ms 8 ms 99.234.60.1
3 7 ms 9 ms 8 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 11 ms 8 ms 209.148.232.229
5 9 ms 12 ms 8 ms 209.148.227.157
6 11 ms 11 ms 11 ms 10.202.47.161
7 * 9 ms * dns.cp.net.rogers.com [64.71.255.204]
8 * 10 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms * * hitronhub.home [192.168.0.1]
2 12 ms 11 ms 8 ms 99.234.60.1
3 7 ms 7 ms 14 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 9 ms 8 ms 10 ms 209.148.232.229
5 11 ms 9 ms 10 ms 209.148.227.157
6 10 ms * 11 ms 10.202.47.161
7 12 ms 10 ms 9 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 * 1 ms 1 ms hitronhub.home [192.168.0.1]
2 14 ms 10 ms 8 ms 99.234.60.1
3 9 ms 7 ms 12 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 12 ms 9 ms 10 ms 209.148.232.229
5 9 ms 8 ms 8 ms 209.148.227.157
6 11 ms 11 ms 10 ms 10.202.47.161
7 * * * Request timed out.
8 8 ms * 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms hitronhub.home [192.168.0.1]
2 10 ms 9 ms 8 ms 99.234.60.1
3 10 ms 9 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 12 ms 13 ms 9 ms 209.148.232.229
5 9 ms 10 ms 9 ms 209.148.227.157
6 * 65 ms 9 ms 10.202.47.161
7 9 ms 7 ms 8 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 64.71.255.204

Tracing route to dns.cp.net.rogers.com [64.71.255.204]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms hitronhub.home [192.168.0.1]
2 11 ms 10 ms 9 ms 99.234.60.1
3 8 ms 11 ms 9 ms 8077-dgw02.hnsn.rmgt.net.rogers.com [66.185.90.57]
4 8 ms 12 ms 10 ms 209.148.232.229
5 10 ms 9 ms 9 ms 209.148.227.157
6 * 11 ms 12 ms 10.202.47.161
7 * * * Request timed out.
8 14 ms * 11 ms dns.cp.net.rogers.com [64.71.255.204]

Trace complete.

 

tracert 2607:f798:18:10:0:640:7125:5204

Tracing route to dns.cp.net.rogers.com [2607:f798:18:10:0:640:7125:5204]
over a maximum of 30 hops:

1 Transmit error: code 1231.

Trace complete.

 

tracert 2607:f798:18:10:0:640:7125:5204

Tracing route to dns.cp.net.rogers.com [2607:f798:18:10:0:640:7125:5204]
over a maximum of 30 hops:

1 Transmit error: code 1231.

Trace complete.


ping -n 50 2607:f798:18:10:0:640:7125:5204

 

Pinging 2607:f798:18:10:0:640:7125:5204 with 32 bytes of data:
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.
PING: transmit failed. General failure.

 

Ping statistics for 2607:f798:18:10:0:640:7125:5204:
Packets: Sent = 50, Received = 0, Lost = 50 (100% loss),

 

Highlighted
I Plan to Stick Around
Posts: 8

Re: Question about Signal Levels

Tech was here today and noted noise at the tap end. Will open ticket with the relevant department - 72 hours to update.

Lost registration on both my VOIP phones and SIP ports were locked.

Waiting on Rogers
Highlighted
Resident Expert
Resident Expert
Posts: 6,829

Re: Question about Signal Levels

@JSS_BRAMPTON did the tech do anything while he was there, swap connectors, check the external cable? Or did he just note the noise problem and kick that along to someone else?

 

Thanks very much for the traces.  They don't contain the data that I was hoping for but thanks very much for giving it a go.  I was hoping that you would see some huge discrepancy from hop #2 (CMTS) or possibly from another router downstream.  There are a couple of higher returns from hop #2 in the group and a single high point in a downstream router, but, thats it.  So, that's a little surprising at this point.  Going to have to think about this .....

 

If and when you have time, can you have a look at the following:

 

1.  Log into your modem and navigate to the BASIC .... GATEWAY FUNCTION tab.  Have a look at the Router mode.  Is it in Dual mode or IPV4 mode?  Thats it for this step. 

 

2.  If the Router mode is in Dual mode, at a command prompt, run the following commands:  

 

ipconfig

 

ipconfig/all

 

What you should see is that the ethernet or wifi adapter has an IPV6 address starting with 2607.  If you look at the following page, the second example (Newer Next) shows the display with IPV6 running. 

 

https://www.cellstream.com/reference-reading/tipsandtricks/121-ipv6-windowslinux-command-line-exampl...

 

So, you should see that the adapter has an IPV6 address or group of IPV6 addresses first, then an IPV4 address.  There may be more than one temporary IPV6 address.  

 

So, if you do see an IPV6 or group of IPV6 addresses starting with 2607 (Rogers), but IPV6 trace and ping is failing, that implies that the CMTS is not configured properly for IPV6 ops.  Yes, you're getting an IPV6 prefix assignment from the CMTS, but, the CMTS isn't allowing IPV6 data to return to the pc.  Thats a CMTS configuration error of some type, which seems to be common these days for some reason. 

 

 

 

 

 

 



Highlighted
I Plan to Stick Around
Posts: 8

Re: Question about Signal Levels

Tech tested my connection, eliminating any backfeed from the other (8+3) subscribers and concluded noise was at the headend level. He ran his tests inside stating all was to spec and after he refers the noise issue to the relevant team, service should improve in 72 hours.

Modem is set on IPv4.

VOIP service acted up again after rebooting modem found SIP ports locked... now a daily painful routine.