AnsweredAssumed Answered

Routing change needed.

Question asked by johnyyc25 on Aug 22, 2012
Latest reply on Aug 22, 2012 by kevinds

Hello,

 

I would like to kindly request that Shaw make a routing change within your network infrastructure.

 

I live in Northeast Calgary and have a server in Seattle. When I perform a traceroute to my machine it is sending my traffic across the continent and back again. This makes absolutely no sense. I work for an ISP and know that it is within your control and can be fixed.

 

Source IP: (Tho it shouldn't matter the source because I get the same result doing the trace from work on a Shaw enterprise connection)

Destination IP:

 

Trace example:

 

john@SSH:~$ traceroute

traceroute to , 30 hops max, 60 byte packets

1  router.home (192.168.0.1)  0.346 ms  0.147 ms  0.214 ms

2  * * *

3  64.59.132.81 (64.59.132.81)  16.788 ms  16.819 ms  16.894 ms

4  rc2nr-pos13-0.wp.shawcable.net (66.163.76.86)  33.274 ms  33.297 ms  33.573 ms

5  rc2so-tge0-15-5-0-1.cg.shawcable.net (66.163.77.202)  51.117 ms  51.080 ms  51.039 ms

6  te1-7.bbr01.eq01.chi01.networklayer.com (206.223.119.63)  46.687 ms  45.730 ms  45.666 ms

7  ae7.bbr02.eq01.chi01.networklayer.com (173.192.18.171)  45.630 ms  43.167 ms  43.453 ms

8  * * *

9  ae7.bbr01.cs01.den01.networklayer.com (173.192.18.168)  82.559 ms  84.238 ms  81.200 ms

10  ae0.bbr01.wb01.sea02.networklayer.com (173.192.18.144)  59.263 ms  59.074 ms  59.674 ms

11  ae0.dar01.sr01.sea01.networklayer.com (173.192.18.199)  80.907 ms ae0.dar02.sr01.sea01.networklayer.com (173.192.18.159)  58.967 ms  60.390 ms

12  po1.fcr02.sr03.sea01.networklayer.com (67.228.118.225)  64.793 ms po2.fcr02.sr03.sea01.networklayer.com (67.228.118.227)  64.800 ms  64.096 ms

13  * * *

14  * * *

15  * * *

16  *^C

john@SSH:~$

 

In theory the traffic should go from Calgary to Vancouver to Seattle or Calgary directly to Seattle. There is no need for it to be going through Winnipeg and then on through Chicago.

 

Cheers,

 

John Bowles

Outcomes