|
[Cable] Strange Tracerouting with New Teksavvy Cable ModemNot sure this is a problem because everything works. But if anyone could give me some understanding of how this is happening it would be appreciated.
Simple Network Setup 192.168.10.10 -> 192.168.10.1 (router) -> 198.84.213.169 (dhcp assigned to router) -> Internet
But when i do a traceroute to google.ca or us WinMTR (74.125.226.120), 64 hops max, 40 byte packets 1 192.168.10.1 (192.168.10.1) 0.971 ms 1.100 ms 1.122 ms 2 * * * 3 209.148.242.185 (209.148.242.185) 10.099 ms 12.117 ms 12.003 ms 4 69.63.249.185 (69.63.249.185) 11.546 ms 10.465 ms 8.054 ms 5 ae1_2150-bdr04-tor.teksavvy.com (69.196.136.164) 12.865 ms 11.845 ms 11.705 ms 6 72.14.212.134 (72.14.212.134) 12.655 ms 11.822 ms 11.152 ms 7 216.239.47.114 (216.239.47.114) 12.668 ms 10.803 ms 11.270 ms 8 209.85.250.207 (209.85.250.207) 11.745 ms 12.723 ms 15.992 ms 9 yyz08s13-in-f24.1e100.net (74.125.226.120) 10.688 ms 11.476 ms 12.043 ms
I had assumed HOP 2 was not pingable till it actually ping'd it which should have been the assigned dhcp address 198.84.213.169.
Anyhow like i said .. everything works i can browse the web etc .. just curious have not see this kind of behavior before |
|
1 edit |
i don't see a CMTS hop in there. i'm betting you have 1 router. the network equip/CMTS is hop 2, and its not responding to pings.
you'll see your routers private address, not the public IP, in a traceroute |
|
TypeS join:2012-12-17 London, ON |
to jholven
The second hop would be the IP address assigned on the WAN side but the CMTS gear it hits after it leaves the cable modem, typically 10.*.*.* or 7.*.*.*.
Perhaps Rogers deprioritized or dropped ICMP traffic on that specific CMTS router. |
|