May 20th 2008
Sierra 875 Aircard using ATT
I
have been critical in the past on local users groups concerning the use
of the Sierra 875 Aircard using ATT telephone service. When I got my
aircard, the local service was through Cingular, and their service
sucked. It dropped calls, had little or no service, even when my cell
phone did have service. When it connected, dialup was faster.
ATT
took over and they actually sped up to a better than dialup speed.
Fewer disconnects and speed was good in a 2G network, and in the city,
speeds approached that of a T1. Not bad.
Still not happy, since
things didn't quite work correctly (VPN didn't work too well) I
continued to try to figure our if latencies and speed unpredictability
were being caused by something in my setup.
I did a trace route to Google's address and what I found, surprised me.
A
trace route is a terminal command which allows you, while connected to
the internet, to trace the way your packet travels to get your answer.
The trouble is that the number of hops is limited and the normal
traceroute does not work.
However, if you use Ubuntu, the
network tools trace route will trace much more. When I used it and did
a traceroute to Google while using the aircard, I found that my route
took me from Columbus Ohio to New York, to London England, to
Amsterdam, and on. No wonder it takes a while to resolve a URL to an IP
address!
Here is some of my output:
Hop
Hostname IP
Time 1 Time 2
1
166.128.127.189
166.128.127.189
0.300ms
1
172.26.248.2
172.26.248.2
1273.418ms
1
172.26.248.2
172.26.248.2
5436.823ms
2
172.16.1.210
172.16.1.210
1526.421ms
2
172.16.1.210
172.16.1.210
5729.080ms
3
12.87.42.165
12.87.42.165
1101.394ms
3
12.87.42.165
12.87.42.165
5368.883ms
4
tbr2.dlstx.ip.att.net
12.122.100.74
1042.991ms
4
tbr2.dlstx.ip.att.net
12.122.100.74
365.494ms
5
ggr3.dlstx.ip.att.net
12.123.16.197
378.919ms
6
att-gw.dallas.level3.net
192.205.34.138
338.911ms
7
vlan99.csw4.Dallas1.Level3.net
4.68.19.254
379.232ms
8
ae-92-92.ebr2.Dallas1.Level3.net
4.69.136.149
349.933ms
9
ae-6.ebr3.NewYork1.Level3.net
4.69.137.122
369.899ms
10
ae-93-93.csw4.NewYork1.Level3.net
4.69.134.110
389.909ms
11
ae-91-91.ebr1.NewYork1.Level3.net
4.69.134.77
369.936ms
12
ae-44.ebr2.London1.Level3.net
4.69.137.77
479.833ms
13
ae-2.ebr2.Amsterdam1.Level3.net
4.69.132.134
470.871ms
14
ae-21-52.car1.Amsterdam1.Level3.net
4.68.120.47
469.933ms
15 no
reply *
16 no
reply *
I
don't understand all I know, but it looks to me that for an unknown
reason, ATT is sending my request for a Google page to Europe and back.
No wonder we have problems!
|
|
|
|
 |
