Re: ath5k: can't browse at all.

["Luis R. Rodriguez" <lrodriguez@atheros.com>]

On Sun, Nov 30, 2008 at 08:53:36AM -0800, Irwan Siajadi wrote:
> --- On Tue, 11/25/08, Pavel Roskin <proski@gnu.org> wrote:
> 
> > From: Pavel Roskin <proski@gnu.org>
> > Subject: Re: ath5k: can't browse at all.
> > To: "Irwan Siajadi" <dev.bahamot@yahoo.com>
> > Cc: linux-wireless@vger.kernel.org
> > Date: Tuesday, November 25, 2008, 8:02 PM
> > On Tue, 2008-11-25 at 09:24 -0800, Irwan Siajadi wrote:
> >
> > > Further testing shows that if I change from WPA2/AES
> > to WPA/TIKIP, I
> > > can finally browse. But it's still hit and missed,
> > I need to reload
> > > the pages once or twice before the pages can load
> > properly.
> >
> > Try disabling hardware crypto in the driver:
> >
> > rmmod ath5k
> > modprobe ath5k nohwcrypt=1
> 
> Sorry for the late reply, being busy with other stuffs.
> Anyway, disabling hardware cyrpto didn't make any changes.
> 
> >
> > In any case, check messages from wpa_supplicant.  Maybe
> > it's
> > reauthenticating very often.  If you flood ping the router
> > ("ping -f"),
> > you would probably see growing dots that represent lost
> > packets.
> 
> Flood ping the router doesn't have any lost packets (although only for a
> minute or so). And my router's log shows that the laptop didn't
> re-authenticate very often.
> 
> I've also compiled vanilla 2.6.26 and 2.6.27 with ath5k (compat-wireless).
> 
> - 2.6.26.8 + ath5k (compat-wireless-old-2008-11-29, files last editted on
> 2008-09-16):
> -> ping shows some packets loss.
> -> can browse any websites.

Lets focus on >= 2.6.27.

> 
> - 2.6.27.7 + ath5k (compat-wireless-2008-11-26):
> -> ping doesn't have any packet loss.
> -> can't browse, browser always waiting for the response from the server.
> Monitoring the traffics shows that there are tx packets, but there's no rx
> packets.
> 
> Anything else I can try?

You say you can ping fine but... browsing doesn't work?? Maybe a
firewall issue?

/etc/init.d/iptables stop

I agree with Pavel this does not seem like a driver issue. Do you have
your AP configured to disable :80 TCP communication? Can you try a simple
netcat server and netcat client on different ports and also on port 80
just to see if its really firewall/AP configuration.

  Luis