"Lasse" <(E-Mail Removed)> hath wroth:
>I have a location with more that one access point.
Is that 2, 3, 4, 5, or more access points? Can we be a bit less
vague? (Yes, it makes a difference).
>THe users on the location
>feel a bad connection - and sometimes they are kicked off the wireles
>network.
The connection has to be lost for a long time in order for the access
point to initiate a disconnect. Since I have no clue what hardware is
being used, I can't offer any suggestions on how to increase the time
to disconnect.
> When I look with Netsumbler I get this screen:
>http://www.kalsen.dk/signal.jpg
That looks fairly normal.
>Why do I see all the black lines in the dump.?.
Collisions, interference, signals from outer space. Basically, the
black lines are packet loss the ocurrs when a noise or interference
hit coincides with a probe request from Netstumbler or a response from
the unspecified access point.
>There are not to many access points close to each other (the other have a
>very small signal and are on nonoverlapping channels).
If they're on non-overlapping channels, they should be seen or heard
on your access point. It's the ones with the "very small signal" that
are probably causing some problems.
>Do you have any clue about this?. Have you seen it somewhere before?
Sure, but you're doing it wrong. Use ping instead of Netstumbler. It
will give you real numbers. Also, Netstumbler indicates signal
strength, which is not by itelf a good indication of packet loss or
reliability. You can have a very strong signal, but a little
interference will still cause considerable packet loss.
Actually, use fping or some other ping probe that's better than the
marginal ping shipped with Windoze.
<http://www.kwakkelflap.com/fping.html> (Windoze)
<http://fping.sourceforge.net> (Linux)
Ping your access point or nearby router. If you see something like
this mess:
Reply[19] from 192.168.1.50: bytes=32 time=2.3 ms TTL=127
Reply[20] from 192.168.1.50: bytes=32 time=38.4 ms TTL=127
Reply[21] from 192.168.1.50: bytes=32 time=34.7 ms TTL=127
Reply[22] from 192.168.1.50: bytes=32 time=2.4 ms TTL=127
Reply[23] from 192.168.1.50: bytes=32 time=2.5 ms TTL=127
Reply[24] from 192.168.1.50: bytes=32 time=2.6 ms TTL=127
Reply[25] from 192.168.1.50: bytes=32 time=2.5 ms TTL=127
Reply[26] from 192.168.1.50: bytes=32 time=22.9 ms TTL=127
Reply[27] from 192.168.1.50: bytes=32 time=19.0 ms TTL=127
Reply[28] from 192.168.1.50: bytes=32 time=2.4 ms TTL=127
Reply[29] from 192.168.1.50: bytes=32 time=2.3 ms TTL=127
then you have an interference problem. "Normal" ping time is about
2.5 msec. However the larger delays are caused by retransmissions
induced by interfernce, reflections, co-channel users, noise, etc. If
you let it run for a while, you'll probably see a pattern. If you
have traffic at the same time, ICMP ping will probably be at a lower
priority and the packets will be lost or delayed. Try it without any
traffic if possible. It's also fun to graph the results.
Good luck.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558