On Fri, 30 Dec 2005 at 11:00 -0700, Dave wrote: > Hans Fugal wrote: > > >On Thu, 29 Dec 2005 at 20:27 -0700, Dave wrote: > > > > > >>You might find out an IP address to the Access point he connects to. > >> > > > > > You have to call your wisp to get the IP of the AP. It is probaly on > another subnet.
So the one reported by traceroute isn't it?
$ traceroute google.com
traceroute to google.com (64.233.187.99), 64 hops max, 40 byte packets
1 ungol (172.17.64.1) 2.593 ms 1.655 ms 1.110 ms
2 fw-asphalt.internal.sbtnet.com (10.8.7.1) 8.506 ms 6.978 ms 8.518 ms
3 69.146.125.1 (69.146.125.1) 7.806 ms 6.382 ms 7.080 ms
4 69.146.239.57 (69.146.239.57) 9.423 ms 10.324 ms 9.742 ms
5 69.146.239.1 (69.146.239.1) 24.407 ms 21.573 ms 23.337 ms
6 0.so-0-3-0.gw6.den4.alter.net (65.206.180.249) 26.868 ms 31.423 ms
68.896 ms
7 0.so-5-1-0.xl2.den4.alter.net (152.63.88.122) 27.118 ms 26.744 ms 41.142
ms
8 0.so-3-0-0.xl2.scl2.alter.net (152.63.48.94) 66.694 ms 54.395 ms 52.465
ms
9 0.so-7-0-0.br1.scl2.alter.net (152.63.57.101) 52.636 ms 53.150 ms 52.848
ms
10 204.255.173.42 (204.255.173.42) 52.938 ms 56.629 ms 56.597 ms
11 so-1-2-0.bbr2.sanjose1.level3.net (209.244.3.141) 67.418 ms 53.911 ms
52.573 ms
12 ae-0-0.bbr2.atlanta1.level3.net (64.159.1.46) 92.514 ms
as-1-0.bbr1.atlanta1.level3.net (209.247.9.101) 92.460 ms
ae-0-0.bbr2.atlanta1.level3.net (64.159.1.46) 97.982 ms
13 ae-11-55.car1.atlanta1.level3.net (4.68.103.130) 92.823 ms
ae-11-53.car1.atlanta1.level3.net (4.68.103.66) 92.972 ms
ae-21-52.car1.atlanta1.level3.net (4.68.103.34) 93.945 ms
14 4.78.208.2 (4.78.208.2) 92.894 ms 4.78.212.66 (4.78.212.66) 92.431 ms
unknown.level3.net (63.211.121.30) 94.933 ms
15 66.249.95.125 (66.249.95.125) 92.822 ms 72.14.236.19 (72.14.236.19)
101.765 ms 66.249.95.125 (66.249.95.125) 130.405 ms
16 216.239.49.226 (216.239.49.226) 100.372 ms 72.14.236.15 (72.14.236.15)
94.336 ms 96.264 ms
17 216.239.49.222 (216.239.49.222) 102.701 ms 64.233.187.99 (64.233.187.99)
97.900 ms 216.239.49.222 (216.239.49.222) 122.314 ms
1 is the linksys. 2 I'm guessing is the AP (it's the one that doesn't
respond to ping). 3 has packet loss. At this moment, I'm seeing under
10ms to 3, usually. (occasional packets as high as 25ms)
> The next best thing is to ping the gateway, You should have a sub 50ms
> ping time. Not sure what CPE you have but if you can login to it you
> want most of them have a rating on signal quality, You need above a 45
> rating.
I'm not sure what CPE means. Here's stats from the linksys:
eth1 IEEE 802.11-DS ESSID:"Mordor"
Mode:Master Frequency:2.437 GHz Access Point: 00:13:10:0D:BF:42
Tx-Power:19 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:4008-7882-41
Link Noise level:-12 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:386 Invalid misc:0 Missed beacon:0
> Try pinging your Gateway, more then 1% packett loss is a bad thing.
So 10-20 and as much as 50 is definitely a bad thing. :-)
> If you are looking for some cool reading try googling "FAST tcp V3".
What will that tell/teach me?
> >No digis out here in Vernal. In fact, the only 802.11* signal I pick up
> >
>
> 802.11 = 2.4
Yes, exactly.
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
signature.asc
Description: Digital signature
/* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
