jdieckmann@valleycountyhospital.org hath wroth:

>Wow, thanks for the detailed reply. Unfortunately, my knowledge of
>TCP/IP is still a bit limited, so when I try to interpret Ethereal
>logs, my head starts to hurt because I have a hard time figuring out
>what I'm looking at. I've also only briefly played with SNMP, though
>I'd be willing to give it a go if it will help me figure out what is
>causing the link to be so slow.

The most important test is finding out what type of traffic is moving
on the wireless. Install a HUB (not a switch) at one end of the
wireless bridge. Sniff with WireShark. You can get a fair idea of
the type of traffic from the IP socket numbers. 80 is http, 21 is
ftp, 443 is MS Netoworking, outgoing email is 25, incoming email is
110, etc. You should be able to get a picture of what ports are being
used and how many bytes are moving. If WireShark is too daunting, try
one of these network monitoring tools:
<http://www.slac.stanford.edu/xorg/nmtf/nmtf-tools.html>
Maybe start with Ntop (for Linux):
<http://www.ntop.org/ntop.html>
There's a Windoze port somewhere out there.

Also, do the IPerf speed test. That will tell you if your wireless is
operating normally.

My guess(tm) is that you have a bandwidth bottleneck at the wireless,
compounded by excessive and uncontrolled traffic over the wireless
link. You're NOT going to get gigabit ethernet performance from a
wireless link that will go perhaps 25Mbits/sec (in one direction at a
time) maximum.

Good luck and either learn quickly or get some experienced help.

--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558