From: Kalle Valo <kvalo@adurom.com>
To: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wl1251 issues
Date: Wed, 04 Aug 2010 21:33:59 +0300 [thread overview]
Message-ID: <87y6cmcjmw.fsf@purkki.adurom.net> (raw)
In-Reply-To: <1280682326.3868.37.camel@gnutoo-laptop> (Denis Carikli's message of "Sun\, 01 Aug 2010 19\:05\:26 +0200")
Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> writes:
> Hi,
Hi Denis,
> Here's the issue(this first issue doesn't involve PSM yet):
> I connect trough wpa to the local access point at the wifi cafee(wrt54
> somrthing,running an old openwrt with a 2.4 kernel and the proprietary
> broadcom module)
>
> I use dhcp to get an ip
> The connection last for a while and then I've that:
> wlan0 IEEE 802.11bg ESSID:"essid_has_been_hidden_in_that_mail"
> Mode:Managed Frequency:2.432 GHz Access Point:
> 00:23:69:XX:XX:XX
> Bit Rate=1 Mb/s Tx-Power=20 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=43/70 Signal level=-67 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> That seem connected.
>
> root@htcdream ~ # ping 192.168.2.1
> PING 192.168.2.1 (192.168.2.1): 56 data bytes
> ^C
> --- 192.168.2.1 ping statistics ---
> 22 packets transmitted, 0 packets received, 100% packet loss
So basically what happens is that you associate but no data is
transfered? Did you confirm that the dhcp client really gets the ip
address?
> here's the wpa connection script output:
> ot@htcdream ~ # sh wpa.sh
> CTRL-EVENT-SCAN-RESULTS
> Trying to associate with 00:23:69:xx:xx:xx
> (SSID='essid_has_been_hidden_in_that_mail' freq=2432 MHz)
> Associated with 00:23:69:xx:xx:xx
> WPA: Key negotiation completed with 00:23:69:xx:xx:xx [PTK=CCMP
> GTK=CCMP]
> CTRL-EVENT-CONNECTED - Connection to 00:23:69:xx:xx:xx completed (auth)
> [id=0 id_str=]
>
> the essid and mac address have been changed.
>
> a while true;do dmesg -c;done gave a still flowing flow of messages:
> here's a part of it:
I didn't immeadiately notice anything wrong from the logs. I would
like to know if the problem is related to power save mode or
encryption. Can you first test without encryption, ie. connect to an
open network and see if you still see the problem. If you still see
the problem, disable power save and connect to the same open AP again.
--
Kalle Valo
prev parent reply other threads:[~2010-08-04 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 17:05 wl1251 issues Denis 'GNUtoo' Carikli
2010-08-04 18:33 ` Kalle Valo [this message]
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=87y6cmcjmw.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=GNUtoo@no-log.org \
--cc=linux-wireless@vger.kernel.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).