On Fri, Nov 26, 2010 at 4:07 AM, Giacomo Comes <[email protected]> wrote:
> On Thu, Nov 25, 2010 at 07:12:28PM +0000, Dave Kilroy wrote:
>>
>> > Attached you will find the wpa_supplicant.log created with the
>> > following command line:
>> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
>>
>> <paste>
>> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver
>> 'default' ctrl_interface 'N/A' bridge 'N/A'
>> ...
>> WEXT: cfg80211-based driver detected
>> ...
>> Driver did not support SIOCSIWENCODEEXT
>> </paste>
>>
>> eh? This looks like the problem. The driver should definitely support
>> this via the cfg80211 wrappers.
>>
>> You might try explicitly forcing wpa_supplicant to use the WEXT driver
>> with -Dwext, though I think the netlink interface ought to work as
>> well.
>
> Done. wpa_supplicant.log looks exactly the same except the line:
> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
> is replaced with:
> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
> as it should be.
>
> One thing that I forgot to mention is that when I run wpa_supplicant,
> on the standard error are printed the following messages:
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCGIWSCAN]: Resource temporarily unavailable
> ioctl[SIOCSIWSCAN]: Device or resource busy
> ioctl[SIOCSIWSCAN]: Device or resource busy
> ioctl[SIOCSIWSCAN]: Device or resource busy
> and so on until I interrupt wpa_supplicant.
>
>>
>> Check whether CONFIG_CFG80211_WEXT is configured in your kernel (it should be).
>
> It is.
>
>>
>> Also ensure that you're not trying to use CCMP. orinoco only supports
>> WPA with TKIP encryption.
>
> wpa_supplicant.conf contains:
> network={
> ? ? ? ?ssid="Comes"
> ? ? ? ?psk="<password>"
> ? ? ? ?key_mgmt=WPA-PSK
> ? ? ? ?priority=5
> ? ? ? ?proto=WPA
> }
Just had a closer look at your log. wpa_supplicant is clearing keys 4
and 5, which is why you're getting invalid arguments reported. This
shouldn't affect driver behaviour.
After that, something seems to go wrong with scanning. Try a plain
scan with wpa_supplicant turned off. Do you get any results?
iw dev eth1 scan
iwlist eth1 scan
Dave.
On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
>
> Just had a closer look at your log. wpa_supplicant is clearing keys 4
> and 5, which is why you're getting invalid arguments reported. This
> shouldn't affect driver behaviour.
>
> After that, something seems to go wrong with scanning. Try a plain
> scan with wpa_supplicant turned off. Do you get any results?
>
> iw dev eth1 scan
> iwlist eth1 scan
>
> Dave.
After a reboot and without configuring the wireless interface,
iw dev eth1 scan
gives:
command failed: Network is down (-100)
and
iwlist eth1 scan
gives:
eth1 Interface doesn't support scanning : Network is down
I was trying to associate the wireless card using iwconfig:
iwconfig eth1 mode managed key <key>
iwconfig eth1 essid <essid>
but the card does not associate with the AP.
Isn't that supposed to work or am I missing something?
Buy the way, if I configure the wireless interface with yast
using WEP (the only way I can make the truemobile
card work) then iw dev eth1 scan gives:
BSS 00:18:f8:c6:04:05 (on eth1)
TSF: 21366823341 usec (0d, 05:56:06)
freq: 2412
beacon interval: 100
capability: ESS Privacy PBCC (0x0051)
signal: -60.00 dBm
last seen: 88 ms ago
SSID: ssid1
Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
DS Parameter set: channel 1
ERP: NonERP_Present Use_Protection Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
BSS 00:13:10:aa:89:4b (on eth1)
TSF: 12179691 usec (0d, 00:00:12)
freq: 2437
beacon interval: 100
capability: ESS Privacy PBCC ShortSlotTime (0x0451)
signal: -27.00 dBm
last seen: 48 ms ago
SSID: ssid2
Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
DS Parameter set: channel 6
ERP: Barker_Preamble_Mode
Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
WPA: * Version: 1
* Group cipher: TKIP
* Pairwise ciphers: TKIP
* Authentication suites: PSK
and iwlist eth1 scan gives:
eth1 Scan completed :
Cell 01 - Address: 00:18:F8:C6:04:05
Channel:1
Frequency:2.412 GHz (Channel 1)
Quality=58/70 Signal level=-52 dBm
Encryption key:on
ESSID:"ssid1"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=0000000504cfa466
Extra: Last beacon: 248ms ago
IE: Unknown: 00076C696E6B737973
IE: Unknown: 010582848B962C
IE: Unknown: 030101
IE: Unknown: 2A0107
IE: Unknown: 32080C1218243048606C
Cell 02 - Address: 00:13:10:AA:89:4B
Channel:6
Frequency:2.437 GHz (Channel 6)
Quality=70/70 Signal level=-27 dBm
Encryption key:on
ESSID:"ssid2"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000000bf9a76e
Extra: Last beacon: 208ms ago
IE: Unknown: 0005436F6D6573
IE: Unknown: 010582848B962C
IE: Unknown: 030106
IE: Unknown: 2A0104
IE: Unknown: 32080C1218243048606C
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
I hope this help.
Giacomo
On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <[email protected]> wrote:
> On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
>>
>> Just had a closer look at your log. wpa_supplicant is clearing keys 4
>> and 5, which is why you're getting invalid arguments reported. This
>> shouldn't affect driver behaviour.
>>
>> After that, something seems to go wrong with scanning. Try a plain
>> scan with wpa_supplicant turned off. Do you get any results?
>
> After a reboot and without configuring the wireless interface,
> iw dev eth1 scan
> gives:
> command failed: Network is down (-100)
The interface need to be up to scan:
ifconfig eth1 up
> I was trying to associate the wireless card using iwconfig:
> ? ?iwconfig eth1 mode managed key <key>
> ? ?iwconfig eth1 essid <essid>
> but the card does not associate with the AP.
> Isn't that supposed to work or am I missing something?
Was that AP using WEP or WPA? The former should work (with the
interface up, and all the parameters being set correctly). The latter
won't.
> Buy the way, if I configure the wireless interface with yast
> using WEP (the only way I can make the truemobile
> card work) then iw dev eth1 scan gives:
> BSS 00:13:10:aa:89:4b (on eth1)
> ? ? ? ?TSF: 12179691 usec (0d, 00:00:12)
> ? ? ? ?freq: 2437
> ? ? ? ?beacon interval: 100
> ? ? ? ?capability: ESS Privacy PBCC ShortSlotTime (0x0451)
> ? ? ? ?signal: -27.00 dBm
> ? ? ? ?last seen: 48 ms ago
> ? ? ? ?SSID: ssid2
> ? ? ? ?Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
> ? ? ? ?DS Parameter set: channel 6
> ? ? ? ?ERP: Barker_Preamble_Mode
> ? ? ? ?Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
> ? ? ? ?WPA: ? ? * Version: 1
> ? ? ? ? ? ? ? ? * Group cipher: TKIP
> ? ? ? ? ? ? ? ? * Pairwise ciphers: TKIP
> ? ? ? ? ? ? ? ? * Authentication suites: PSK
That's what I wanted to see. So the card is able to scan, but your
wpa_supplicant log indicates it is continuously timing out the scans.
I don't know what is going on there.
What you can try is to turn off wpa_supplicant roaming, and force
wpa_supplicant to connect to the AP with highest priority in your
config. Set ap_scan=2 in wpa_supplicant.conf, and set
group=TKIP
pairwise=TKIP
in the network block.
This also prevents wpa_supplicant trying to connect to an AP using
BSSID, which the agere cards don't support.
Dave.
On Wed, Dec 01, 2010 at 09:52:15PM +0000, Dave Kilroy wrote:
> On Tue, Nov 30, 2010 at 2:19 AM, Giacomo Comes <[email protected]> wrote:
> > On Sun, Nov 28, 2010 at 04:10:30PM +0000, Dave Kilroy wrote:
> >>
> >> Just had a closer look at your log. wpa_supplicant is clearing keys 4
> >> and 5, which is why you're getting invalid arguments reported. This
> >> shouldn't affect driver behaviour.
> >>
> >> After that, something seems to go wrong with scanning. Try a plain
> >> scan with wpa_supplicant turned off. Do you get any results?
> >
> > After a reboot and without configuring the wireless interface,
> > iw dev eth1 scan
> > gives:
> > command failed: Network is down (-100)
>
> The interface need to be up to scan:
>
> ifconfig eth1 up
Ok, my bad. After I put the interface up the scan works.
>
> > I was trying to associate the wireless card using iwconfig:
> > ? ?iwconfig eth1 mode managed key <key>
> > ? ?iwconfig eth1 essid <essid>
> > but the card does not associate with the AP.
> > Isn't that supposed to work or am I missing something?
>
> Was that AP using WEP or WPA? The former should work (with the
> interface up, and all the parameters being set correctly). The latter
> won't.
The AP was using WEP, but it didn't associate because I didn't put up
the interface. After doing it, it works.
>
> > Buy the way, if I configure the wireless interface with yast
> > using WEP (the only way I can make the truemobile
> > card work) then iw dev eth1 scan gives:
> > BSS 00:13:10:aa:89:4b (on eth1)
> > ? ? ? ?TSF: 12179691 usec (0d, 00:00:12)
> > ? ? ? ?freq: 2437
> > ? ? ? ?beacon interval: 100
> > ? ? ? ?capability: ESS Privacy PBCC ShortSlotTime (0x0451)
> > ? ? ? ?signal: -27.00 dBm
> > ? ? ? ?last seen: 48 ms ago
> > ? ? ? ?SSID: ssid2
> > ? ? ? ?Supported rates: 1.0* 2.0* 5.5* 11.0* 22.0
> > ? ? ? ?DS Parameter set: channel 6
> > ? ? ? ?ERP: Barker_Preamble_Mode
> > ? ? ? ?Extended supported rates: 6.0 9.0 12.0 18.0 24.0 36.0 48.0 54.0
> > ? ? ? ?WPA: ? ? * Version: 1
> > ? ? ? ? ? ? ? ? * Group cipher: TKIP
> > ? ? ? ? ? ? ? ? * Pairwise ciphers: TKIP
> > ? ? ? ? ? ? ? ? * Authentication suites: PSK
>
> That's what I wanted to see. So the card is able to scan, but your
> wpa_supplicant log indicates it is continuously timing out the scans.
> I don't know what is going on there.
>
> What you can try is to turn off wpa_supplicant roaming, and force
> wpa_supplicant to connect to the AP with highest priority in your
> config. Set ap_scan=2 in wpa_supplicant.conf, and set
>
> group=TKIP
> pairwise=TKIP
>
> in the network block.
>
> This also prevents wpa_supplicant trying to connect to an AP using
> BSSID, which the agere cards don't support.
>
Running:
wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd
wpa_supplicant.conf content:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
ap_scan=2
network={
ssid="Comes"
psk="<password>"
key_mgmt=WPA-PSK
priority=5
proto=WPA
group=TKIP
pairwise=TKIP
}
wpa_supplicant.log attached.
Giacomo