Traduisez - Übersetzen - Traduzca - Traduza - Tradurre - Translate

VanLUG Email Archive

Re: @Home/ADSL routing

Jeff Alami
Sun, 13 Sep 1998 11:00:03 -0700

Tim Baur wrote:
>
> On Sat, 12 Sep 1998, slava voronin wrote:
>
> > I am using wave , can you please say about difference in routing with
> > adsl.
>
> @Home routes via Sprint. Which 75% of the time does =not= have stable
> routing. Sprint's internal routing is extremly lame. Their routing to the
> US, isnt at all that great to say the least. It's been this way for along
> time. I have never been impressed with sprint's network. I could go on and
> on forever bitching about sprint.
>
> Very lame internal routing. There might be a reason, but it is still lame
> networking either way. Especially considering the traffic runs down to the
> US first, before reaching the end destination.
>
> ADSL routes via BCTel. BCTel peer's with MCI and now Starcom (who peers
> with Above). Granted the MCI line isnt that perfect to due the load on the
> *.SanFrancisco.mci.net routers. However since BCTel is multihomed, it
> provides alternate routes for the traffic, picking the shortest path. Even
> without the Starcom peer, BCTel still has better routing.
>
> But every uplink has their moments. Not everything is perfect.
>

Yes, the routing does bite. I'm using @Home and there are problems with
that. @Home and Rogers will be moving over to BCTel/MCI/Starcom's link
in Harbour Tower (or someplace else, not sure) so that the routing will
be significantly better. Suppose I traceroute from my host in Harbour
Tower to an @Home link:

traceroute to cr528701-a.crdva1.bc.wave.home.com (24.113.3.19), 30 hops
max, 40 byte packets
1 gw1-0.netnation.com (204.174.223.254) 0.578 ms 1.139 ms 0.47 ms
2 eth-netnation.com (209.153.195.161) 1.602 ms 2.34 ms 1.664 ms
3 atm60.3-oc3-sea.starcom.net (209.153.195.66) 4.868 ms 5.009 ms
4.996 ms
4 sl-gw6-sea-6-0-0-T3.sprintlink.net (144.224.113.1) 5.478 ms 5.113
ms 4.823 ms
5 sl-bb11-sea-2-2.sprintlink.net (144.232.6.69) 4.336 ms 4.799 ms
4.5 ms
6 sl-bb22-stk-4-0.sprintlink.net (144.232.8.29) 20.567 ms 20.577 ms
21.182 ms
7 sl-bb21-stk-8-0.sprintlink.net (144.232.4.113) 19.769 ms 21.299
ms 20.067 ms
8 sl-bb2-stk-0-0-0.sprintlink.net (144.232.4.70) 20.705 ms 20.865
ms 20.365 ms
9 sl-w1-mae-0-1-0-45M.sprintlink.net (144.228.10.110) 23.445 ms
24.651 ms 23.168 ms
10 bb1.mae-w-sj.home.net (198.32.136.142) 25.557 ms 25.215 ms 25.605
ms
11 172.16.2.130 (172.16.2.130) 82.309 ms 108.097 ms 68.376 ms
12 172.16.4.58 (172.16.4.58) 111.029 ms 86.698 ms 69.55 ms
13 r1-fe0-0-100bt.rdc1.bc.wave.home.net (24.2.10.2) 75.558 ms 51.287
ms 60.368 ms
14 10.0.186.2 (10.0.186.2) 68.481 ms 51.292 ms 71.202 ms
15 cr528701-a.crdva1.bc.wave.home.com (24.113.3.19) 79.238 ms 65.32
ms 89.96 ms

When @Home does move over to the BCTel/Starcom network (and I know
they're doing it; they sent me a message that their move to the new
network might cause some downtime), you'll practically be able to skip
routers 4 through 12 or so (maybe a couple more will be added). In other
words, it'll be very good routing.

-- 
Jeff Alami, Senior Consultant
Guardian Consulting Services