Posted: Tue Nov 25, 2008 1:34 Post subject: ar430w = Strange latency, ping timeouts, what is going on?
Folks,
I'm a longish-time user of DD-WRT on Buffalo equipment. Been using it for a long time with great success. Today, I decided to deploy an Airlink ar430w for a project because the router was $14.95 at Fry's and it's on the DD-WRT list. (I am not replacing any Buffalo gear, this is a side project for a client.)
After flashing, no apparent problems in the UI. When I got around to testing it, that's a whole other story. Configuration is basic AP mode, no DHCP server (getting DHCP leases from Win2K3 DHCP server).
So it's up, broadcasting an SSID, and I can associate to it no sweat.
The following problems occur either via wireless or wired -- any time I am going through the ar430w this happens. So I doubt it's the radio.
The problems:
1. I can ping servers only sporadically. Packet loss appears to be 90% on wireless, 60% on wired.
2. When pinging the AP management IP itself, sometimes I see huge latency spikes in the 300-500ms range for 5-10 seconds at a time, sometimes the requests time out.
3. And I think this is related, but my mobile phone cannot obtain an IP, or it times out. It can associate just fine, but it never gets an IP.
This is all very strange. I've never had any problems with Buffalo hardware. Now I feel as if I may be up the creek with a lemon Airlink.
Posted: Wed Nov 26, 2008 9:29 Post subject: Router or AP
Are you using it as a router or an AP?
If you are running AP only, there is a known bug with ARP handling. Even if you are only running as an access point, activate the WAN port... do NOT leave it disabled.
That is a workaround. I don't know when it will be fixed.
The latest version 111908 unstable on client Brigde and Brigde... lost connection with main route as well as internet somehow... I would wait for the fix.
Posted: Wed Nov 26, 2008 21:31 Post subject: Re: Router or AP
remaker wrote:
Are you using it as a router or an AP?
If you are running AP only, there is a known bug with ARP handling. Even if you are only running as an access point, activate the WAN port... do NOT leave it disabled.
That is a workaround. I don't know when it will be fixed.
That was very helpful, thanks! We're working correctly now, as I expected.
Should I revert back to SP1 or stick with this current pre-SP2 release?
