On 2/16/2012 5:41 AM, Chuck Banshee wrote:
> I'm debugging slow speeds with my WISP connection; so I just ran the new
> google Network Diagnostic Tool:
> One output statement from Google NDT I don't understand is:
> "Network congestion may be limiting the connection."
> Does this mean other (i.e., not mine) traffic on my network?
> Does it mean other computers' traffic on my network? (i.e., my household)
> Does it mean other people's traffic within the WISP private network?
> Does it mean a background program is running on my PC?
> Q: What does that output statement indicate?
> Network congestion may be limiting the connection.
> Note: I also get that same statement from the UC Santa Cruz NDT server:
I can't imagine much network traffic at 5:41AM. That makes me wonder
about Jeff microwave oven theory, since you are doing this at what is
known as "Oh dark thirty" or "stupid O clock."
Incidentally, I get a message from that diagnostic that about half the
time the receiver buffer is causing congestion on my system. There is a
program called TCP-Z to adjust the buffer size, but I can't get win 7 to
run it due to a certificate issue. Spybot says it is virus free. MS
Security essentials says it is hacker software. Well, doh! Of course it is.
Note with Kismet, you can see if other people using the WISP. What you
want to do is determine what channel you are using, then "park" on that
channel. [I don't have kismet running nearby, so you will have to RTFM.
The idea is you don't want Kismet to hop from channel to channel.] This
may require running wireshark as well.
My guess is Jeff will read this and do a better reply on detecting if
the channel is busy since this is probably fresher in his memory.
Come to think of it, a packet sniffer is mandatory here since there are
two scenarios (at least). One, there is some other traffic to your wisp.
Two, there is some unrelated wifi traffic on the same frequency. In the
boonies, it wouldn't be all that unexpected for somebody to hook up a
point to point link (bridge) to share internet service with a buddy that
can't see the wisp. So you will have to examine the addresses of the
packets. Be sure not to read any clear text.
You are going to be f-ing brilliant when this is all done!