Re: DI 624 revC- severe wireless latency after consistent throughput

>Besides higer latency numbers are you getting slower throughputs (LAN
>or WAN side)? Packet losses? Latency could only be the tip of the
>iceberg. The suggestions below assume this.

For the wireless client, we have slower throughput on the LAN side and
obviously WAN as well as a result of the LAN issues. No packet losses.
It's all going through, just more slowly.

>Have you tried switching channels? Download Netstumbler and verify
>what other networks are flocking around yours. Then choose a channel
>farthest from anyone.

Yep. I've tried channels all over. So far I've only been able to track
neighboring networks with SSID broadcast enabled. Does Netstumbler get
them all? If so, that'll be quite useful. Using the DI624's auto
select, it chose the same channel that I would have given the listing
of neighboring SSIDs (channels 6-11). I selected channel 1. I changed
it around many times to no avail. 3, 4, 8, 11. I'll give Netstumbler a
try though. Thanks.

>Are you using WPA, WEP or none? WPA implementation is not the most
>robust in these routers so for testing purposes you might want to try
>different security setups. If it gets better you know who the culprit
>is and you could try updating your wireless client drivers. Update
>them anyways and see if it does any good.

I had WEP enabled for all my tests. WPA and WPA2 didn't work for me.
Even under the new 2.70 firmware. That said, I didn't put a whole lot
of effort into trying to get those working as this issue was the more
serious one. I didn't try out the unsecured network, mostly because if
that's the problem, I'm not going to use that router in any case. I
have my Netgear router that is more stable with security enabled. I was
just hoping for some better stability, performance and security.
Unfortunately I can't seem to find it.

>How close are you to the DI-624? What walls do you have between you
>and the client? I believe Netstumbler can detect signal intensity and
>signal to noise ratio (have to confirm this). For testing purposes try
>to put the client next to the DI-624.

The router and wireless client are about 20ft away. Maybe less. There
is 1 wall between the router and client. I live in a condo (1300sqft)
so distance won't be huge. I will try out that Netstumbler program and
see if there are any hidden neighboring networks (hopefully it can
detect it).

>Are there possible interference sources close by? Cordless phones,
>bluetooth devices, microwave ovens? Maybe airports, weather stations
>or military bases? The S radar band is between 2-4 GHz and is used by
>terminal air traffic control, long range weather and marine radar; the
>DI-624 uses 2.4 GHz.

Nope. There is only a 5.4GHz phone in the living room (12ft away).

>Is there a pattern in the daytime when performance starts to decrease?
>There is a little app called PingPlotter that will ping continuously
>to a source and plot it in a chart. This could point to your neighbors
>or yourself turning something on at a specific time of day.

It happens soon after we initiate a P2P connection. Any time of day
really. Obviously it happens more frequently during peak hours since
those are the times when we're using the connection the most as well.
But I've had it crop up during offpeak hours as well. 4am, 10am, etc.

>In context this also suggests that you are facing a location specific
>problem. You could try taking your setup to a parents or friend's
>house and see if the problem persists.

Maybe. But my hunch is on something else. Specifically the fact that
DI624 does not handle multiple simultaneous connections very well. My
Netgear runs fine for 2 months before it needs a reset. The Linksys was
having packet loss but latency was low. DI624 is having high latency
only when there is steady activity.

Netstumbler looks promising. I'll give that a go and we'll see what we
find out. Thanks!

.

Relevant Pages