linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Irwan Siajadi <dev.bahamot@yahoo.com>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
	Pavel Roskin <proski@gnu.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath5k: can't browse at all.
Date: Mon, 1 Dec 2008 13:36:40 -0800	[thread overview]
Message-ID: <20081201213640.GB6997@tesla> (raw)
In-Reply-To: <63885.52788.qm@web59615.mail.ac4.yahoo.com>

On Mon, Dec 01, 2008 at 07:11:55PM -0800, Irwan Siajadi wrote:
> 
> 
> 
> --- On Mon, 12/1/08, Luis R. Rodriguez <lrodriguez@atheros.com> wrote:
> 
> > From: Luis R. Rodriguez <lrodriguez@atheros.com>
> > Subject: Re: ath5k: can't browse at all.
> > To: "Irwan Siajadi" <dev.bahamot@yahoo.com>
> > Cc: "Pavel Roskin" <proski@gnu.org>, "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
> > Date: Monday, December 1, 2008, 5:11 PM
> > 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.
> 
> 
> Firewall on both end (router-ap and laptop) is disabled.
> I can't do netcat on the server since it's not a PC box. It's an all in
> one unit (ADSL modem+AP+router). But I did wireshark on the laptop before
> reading your email. And I can see many TCP retransmission while trying to
> browse. If you like I can attach the log and send it to you.
> 
> 
> As comparison, I also do wireshark while using ndiswrapper. I can find TCP
> retransmission while using ndiswrapper, but doesn't really affect browsing
> or large file transfer through SMB.
> 
> 
> PS: If you prefer netcat, please tell me, I'll do that and send the log if
> you like.

I'll prefer a very simple netcat log. Do you understand why we find this so
strange? It may help to debug the issue at hand.

  Luis

  reply	other threads:[~2008-12-02  5:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  3:11 ath5k: can't browse at all Irwan Siajadi
2008-12-01 21:36 ` Luis R. Rodriguez [this message]
2008-12-02  7:27   ` Irwan Siajadi
2008-12-02  8:00     ` Luis R. Rodriguez
2008-12-02 13:04       ` Irwan Siajadi
2008-12-07 19:39       ` Irwan Siajadi
  -- strict thread matches above, loose matches on Subject: below --
2008-11-24 17:41 Irwan Siajadi
2008-11-24 18:53 ` Pavel Roskin
2008-11-25  2:36   ` Irwan Siajadi
2008-11-25 17:24   ` Irwan Siajadi
2008-11-25 20:02     ` Pavel Roskin
2008-11-30 16:53       ` Irwan Siajadi
2008-12-01 17:11         ` Luis R. Rodriguez
2008-11-24 18:54 ` Dan Williams
2008-11-25  2:30   ` Irwan Siajadi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081201213640.GB6997@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=dev.bahamot@yahoo.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=proski@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).