Networking Forums

Networking Forums > Computer Networking > Linux Networking > wireless problem: high bandwidth but high latency

Reply
Thread Tools Display Modes

wireless problem: high bandwidth but high latency

 
 
Dan Christensen
Guest
Posts: n/a

 
      01-19-2005, 02:33 AM
I've just purchased a D-Link DI-624 wireless router and am having
trouble getting the wireless network working properly. boots
is connected to the router by ethernet, and itchy is connected
to the router with an 802.11b wireless card.

Symptoms first, then more details about my set-up below.

I can transfer files between the two machines at around 500Kbytes/s, but
get horrible behaviour when I try to ping in one direction:

boots# ping itchy
PING itchy (192.168.1.100) 56(84) bytes of data.
64 bytes from itchy (192.168.1.100): icmp_seq=1 ttl=64 time=4.17 ms
64 bytes from itchy (192.168.1.100): icmp_seq=8 ttl=64 time=962 ms
64 bytes from itchy (192.168.1.100): icmp_seq=9 ttl=64 time=1.84 ms
64 bytes from itchy (192.168.1.100): icmp_seq=10 ttl=64 time=958 ms
64 bytes from itchy (192.168.1.100): icmp_seq=11 ttl=64 time=1.72 ms

--- itchy ping statistics ---
17 packets transmitted, 5 received, 70% packet loss, time 15999ms
rtt min/avg/max/mdev = 1.726/385.777/962.408/469.319 ms


In the other direction, there is no problem:

itchy# ping boots
PING boots (192.168.1.103): 56 data bytes
64 bytes from 192.168.1.103: icmp_seq=0 ttl=64 time=3.4 ms
64 bytes from 192.168.1.103: icmp_seq=1 ttl=64 time=3.2 ms
64 bytes from 192.168.1.103: icmp_seq=2 ttl=64 time=2.9 ms
64 bytes from 192.168.1.103: icmp_seq=3 ttl=64 time=4.0 ms
64 bytes from 192.168.1.103: icmp_seq=4 ttl=64 time=3.2 ms
64 bytes from 192.168.1.103: icmp_seq=5 ttl=64 time=1.9 ms
64 bytes from 192.168.1.103: icmp_seq=6 ttl=64 time=2.9 ms

--- boots ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 1.9/3.0/4.0 ms


And if I ping in both directions simultaneously, then itchy->boots is
still good, and boots->itchy becomes very consistent:

boots:~# ping itchy
PING itchy (192.168.1.100) 56(84) bytes of data.
64 bytes from itchy (192.168.1.100): icmp_seq=1 ttl=64 time=2.99 ms
64 bytes from itchy (192.168.1.100): icmp_seq=2 ttl=64 time=565 ms
64 bytes from itchy (192.168.1.100): icmp_seq=3 ttl=64 time=565 ms
64 bytes from itchy (192.168.1.100): icmp_seq=4 ttl=64 time=565 ms
64 bytes from itchy (192.168.1.100): icmp_seq=5 ttl=64 time=565 ms
64 bytes from itchy (192.168.1.100): icmp_seq=6 ttl=64 time=565 ms
64 bytes from itchy (192.168.1.100): icmp_seq=7 ttl=64 time=565 ms

--- itchy ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6004ms
rtt min/avg/max/mdev = 2.997/485.113/565.880/196.824 ms

The first packet is almost always fast, and the remaining packets
get through when the itchy->boots packets go, so the value 565 ms
depends on the relative timing of the two pings.

Both machines can ping the outside world in about 10 ms and they
can ping the router in 3 ms (wireless) and about 0.3 ms (ethernet).

Details about my set-up:

- Both machines run linux 2.6.10.
- The same problem happens with two other wireless machines on
the network, one at a time. Two of the machines have Compaq WL-110
wireless cards; one has a Dell TrueMobile 1150 Series mini PCI card.
Those two machines run 2.4.26 (or something close to that).
- The same problem happens with pings between two wireless machines
on the network.
- The wireless machines are between 3 and 15 feet from the router,
in the same room, with no obstacles. The router is not right
next to any other equipment.
- I used to have the three wireless machines on an ad hoc network,
and had no problems at all with bandwidth or latency. Now
the wireless cards are in "managed" mode.
- I tried both with and without WEP, and tried adjusting just about
all the other settings on the router.
- The routing tables on both machines look like:

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1

Any thoughts? What other information can I provide?

Thanks for any help,

Dan

--
Dan Christensen
(E-Mail Removed)
 
Reply With Quote
 
 
 
 
dan.christensen@gmail.com
Guest
Posts: n/a

 
      01-19-2005, 02:40 PM
I finally figured this out! I had my wireless cards configured to go
into a powersaving mode, and to only wake up when unicast packets were
received. This meant that arp request packets were ignored! I had
configured the cards this way a couple of years ago and used them since
then on an ad hoc network without any trouble; maybe power management
isn't done in ad hoc mode?

Also not sure why the arp cache wasn't storing things longer...
Dan

--
Dan Christensen
(E-Mail Removed)

 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Using AD in High-Latency satellite networks? FB Windows Networking 3 05-13-2009 11:02 PM
What is your favorite method to troubleshoot high-bandwidth/high latency networks? Spin Windows Networking 15 05-07-2009 08:04 PM
high ping latency correlation with high server activity Tal Bar-Or Windows Networking 0 04-29-2008 08:08 AM
Intermittant high latency Doball Wireless Networks 9 03-17-2006 02:29 AM
High latency with MASQ, not without Ted Behling Linux Networking 1 09-04-2003 01:03 PM



1 2 3 4 5 6 7 8 9 10 11