From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: "Tor Håkon Haugen" <tor.hakon.haugen@gmail.com>,
"Zhu Yi" <yi.zhu@intel.com>,
linux-wireless@vger.kernel.org,
ipw3945-devel@lists.sourceforge.net
Subject: Re: [ipw3945-devel] [BUG] iwlwifi 3945 works only with disable_hw_scan=1
Date: Mon, 16 Jun 2008 10:11:03 +0300 [thread overview]
Message-ID: <48561207.50102@gmail.com> (raw)
In-Reply-To: <48560C38.3030901@gmail.com>
Maxim Levitsky wrote:
> .....
>>
>> I just want to note that hardware scanning doesn't work well here
>> (something unrelated)
>>
>> First of all I noticed large delays in communications occurring
>> sometimes, I for example tried pinging Google, and every 20 replies
>> I get about 10 lost packets. (this is exactly what hardware scanning
>> should prevent, but it seems that the opposite happens)
>>
>> I tried that again now, and see no delays, but I reproduced this twice.
>
> Rebooted, and here it is:
>
> maxim@MOBILE:~$ ping www.google.com
> PING www.google.com (209.85.135.147) 56(84) bytes of data.
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=1 ttl=245
> time=89.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=2 ttl=245
> time=89.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=3 ttl=245
> time=87.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=4 ttl=245
> time=87.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=5 ttl=245
> time=85.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=6 ttl=245
> time=88.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=7 ttl=245
> time=88.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=8 ttl=245
> time=86.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=9 ttl=245
> time=85.8 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=10 ttl=245
> time=89.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=11 ttl=245
> time=88.5 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=12 ttl=245
> time=89.5 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=13 ttl=245
> time=87.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=14 ttl=245
> time=87.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=15 ttl=245
> time=89.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=16 ttl=245
> time=89.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=17 ttl=245
> time=87.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=25 ttl=245
> time=87.8 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=26 ttl=245
> time=89.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=27 ttl=245
> time=87.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=28 ttl=245
> time=89.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=29 ttl=245
> time=85.9 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=30 ttl=245
> time=86.9 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=31 ttl=245
> time=87.8 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=32 ttl=245
> time=87.3 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=33 ttl=245
> time=86.8 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=34 ttl=245
> time=87.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=35 ttl=245
> time=89.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=36 ttl=245
> time=88.2 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=37 ttl=245
> time=87.6 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=38 ttl=245
> time=87.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=39 ttl=245
> time=88.6 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=40 ttl=245
> time=87.6 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=41 ttl=245
> time=86.6 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=42 ttl=245
> time=87.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=43 ttl=245
> time=87.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=44 ttl=245
> time=87.8 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=45 ttl=245
> time=86.3 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=46 ttl=245
> time=86.4 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=47 ttl=245
> time=88.4 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=55 ttl=245
> time=87.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=56 ttl=245
> time=88.4 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=57 ttl=245
> time=87.5 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=58 ttl=245
> time=87.0 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=59 ttl=245
> time=87.6 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=60 ttl=245
> time=87.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=61 ttl=245
> time=88.1 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=62 ttl=245
> time=89.7 ms
> 64 bytes from www.google.com (209.85.135.147): icmp_seq=63 ttl=245
> time=87.1 ms
> ^C
> --- www.google.com ping statistics ---
> 63 packets transmitted, 49 received, 22% packet loss, time 62140ms
> rtt min/avg/max/mdev = 85.770/87.752/89.720/1.068 ms
> maxim@MOBILE:~$
>
> and here:
>
> ping www.google.com
> PING www.l.google.com (209.85.129.99) 56(84) bytes of data.
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=1 ttl=246
> time=82.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=9 ttl=246
> time=79.6 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=10 ttl=246
> time=83.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=11 ttl=246
> time=82.6 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=12 ttl=246
> time=82.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=13 ttl=246
> time=82.1 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=14 ttl=246
> time=81.9 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=15 ttl=246
> time=81.4 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=16 ttl=246
> time=82.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=17 ttl=246
> time=80.9 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=18 ttl=246
> time=80.9 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=19 ttl=246
> time=80.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=20 ttl=246
> time=81.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=21 ttl=246
> time=80.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=22 ttl=246
> time=80.1 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=23 ttl=246
> time=82.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=24 ttl=246
> time=82.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=25 ttl=246
> time=82.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=26 ttl=246
> time=81.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=27 ttl=246
> time=81.5 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=28 ttl=246
> time=81.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=29 ttl=246
> time=80.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=30 ttl=246
> time=80.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=31 ttl=246
> time=80.0 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=39 ttl=246
> time=82.8 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=40 ttl=246
> time=82.3 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=41 ttl=246
> time=81.3 ms
> 64 bytes from www.google.com (209.85.129.99): icmp_seq=42 ttl=246
> time=81.8 ms
> ^C
> --- www.l.google.com ping statistics ---
> 42 packets transmitted, 28 received, 33% packet loss, time 41109ms
> rtt min/avg/max/mdev = 79.627/81.461/83.079/0.961 ms
> maxim@MOBILE:~$
>
>
>>
>> Then power levels go crazy, the nm-applet shows that my access point
>> have 23% quality, then 100%, then something low again, and looking
>> list of networks withing same applet, it shows for example now that
>> all 3 networks (mine, and two neighbors) have 100% quality, which is
>> just wrong.
Just reproduced this with following commands;
(I was playing with packet injection, I use recently posted patch for that)
ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
aireplay-ng --test wlan0
ifconfig wlan0 down
iwconfig wlan0 mode managed
Then I disable/enable wireless in nm-applet, and get something funny:
wlan0 Scan completed :
Cell 01 - Address: 00:1B:9E:D8:77:02
ESSID:"MAXIM-HOME"
Mode:Master
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=234/100 Signal level:-82 dBm Noise level=-28 dBm
Encryption key:on
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=0000000935df8c51
Cell 02 - Address: 00:1A:70:7B:6A:52
ESSID:"basinm"
Mode:Master
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=144/100 Signal level:-82 dBm Noise level=-28 dBm
Encryption key:on
IE: WPA Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
12 Mb/s; 48 Mb/s
Extra:tsf=000000330e1bb608
Cell 03 - Address: 00:0E:2E:F7:A0:3E
ESSID:"Home"
Mode:Master
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=188/100 Signal level:-82 dBm Noise level=-28 dBm
Encryption key:off
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Extra:tsf=000002df7cea679c
MAXIM-HOME is my access point.
Best regards,
Maxim Levitsky
>>
> Don't see that now, but sudo iwlist wlan0 scan shows only my access point,
> although there are two another strong access points.
>
> Best regards,
> Maxim levitsky
>
>>
>> Best regards,
>> Maxim Levitsky
>>
>
next prev parent reply other threads:[~2008-06-16 7:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 15:07 [BUG] iwlwifi 3945 works only with disable_hw_scan=1 Maxim Levitsky
2008-06-12 3:28 ` Zhu Yi
2008-06-12 12:13 ` Maxim Levitsky
2008-06-12 13:59 ` [ipw3945-devel] " John W. Linville
2008-06-12 14:19 ` Maxim Levitsky
2008-06-12 20:25 ` Stephen Clark
2008-06-13 7:35 ` Zhu Yi
2008-06-13 8:48 ` Filippo Zangheri
2008-06-13 12:37 ` Tor Håkon Haugen
2008-06-13 13:03 ` John W. Linville
2008-06-13 14:59 ` Tor Håkon Haugen
2008-06-13 15:06 ` Maxim Levitsky
2008-06-13 15:09 ` Tor Håkon Haugen
2008-06-13 20:04 ` Tomas Winkler
2008-06-14 10:00 ` Maxim Levitsky
2008-06-14 16:50 ` Luis R. Rodriguez
2008-06-15 13:42 ` Maxim Levitsky
2008-06-15 13:47 ` Tomas Winkler
2008-06-15 14:12 ` Maxim Levitsky
2008-06-15 15:09 ` Tomas Winkler
2008-06-15 16:47 ` Tomas Winkler
2008-06-16 5:50 ` Maxim Levitsky
2008-06-16 5:52 ` Tomas Winkler
2008-06-16 6:08 ` Maxim Levitsky
2008-06-16 6:46 ` Maxim Levitsky
2008-06-16 7:11 ` Maxim Levitsky [this message]
2008-06-16 14:35 ` Dan Williams
2008-06-16 21:41 ` Tomas Winkler
2008-06-18 8:28 ` drago01
2008-06-24 19:47 ` John W. Linville
2008-06-24 20:32 ` Maxim Levitsky
2008-06-25 5:43 ` Tomas Winkler
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 15:47 Maxim Levitsky
2008-06-12 2:26 ` [ipw3945-devel] " Zhu Yi
2008-06-12 6:42 ` drago01
2008-06-12 7:08 ` Zhu Yi
2008-06-12 12:48 ` Maxim Levitsky
2008-06-12 14:22 ` Maxim Levitsky
2008-06-12 14:26 ` Norbert Preining
2008-06-12 15:02 ` Dan Williams
2008-06-13 2:00 ` Zhu Yi
2008-06-13 14:45 ` Dan Williams
2008-06-16 1:40 ` Zhu Yi
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=48561207.50102@gmail.com \
--to=maximlevitsky@gmail.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=tor.hakon.haugen@gmail.com \
--cc=yi.zhu@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.