PierreAd
n00b
Joined: 24 Oct 2006
Posts: 12
Location: Lyon, France
|
 Posted: Wed Apr 04, 2007 12:44 pm Post subject: [wifi] ipw2100 in-kernel : connexions impossibles... |
 |
|
Salut tout le monde,
Bon voilà, j'ai vu il y a quelques semaines que le paquet ipw2100 serait supprimé de portage au profit du driver inclus dans le kernel. J'ai donc compilé mon kernel avec le module ipw2100, et toussa... Problème, ma carte wifi est bien reconnue correctement, mais impossible de me connecter à un quelconque réseau, apparemment c'est un problème avec l'encryption (pour info, j'ai bien l'option CONFIG_CRYPTO_ARC4=y dans mon kernel).
dmesg | grep -i ieee
| Code: | ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ieee80211_crypt: registered algorithm 'WEP'
ieee80211_crypt: registered algorithm 'CCMP'
ieee80211_crypt: registered algorithm 'TKIP'
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
eth1: could not initialize WEP: load module ieee80211_crypt_wep
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
eth1: could not initialize WEP: load module ieee80211_crypt_wep
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
ieee80211_crypt_wep: could not allocate crypto API arc4
|
iwconfig eth1
| Code: | eth1 unassociated ESSID:"mon ssid" Nickname:"mon-ssid"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power:16 dBm
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
|
iwlist eth1 scan
| Code: | eth1 Scan completed :
Cell 01 - Address: 00:90:4B:C1:F2:2B
ESSID:"mon-ssid"
Protocol:IEEE 802.11bg
Mode:Master
Channel:11
Encryption key:on
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
48 Mb/s; 54 Mb/s
Quality:89 Signal level:0 Noise level:0
Extra: Last beacon: 200ms ago
|
Et lorsque je tente de lancer une connexion "à la mano", via iwconfig, tout se déroule bien jusqu'à ce que je précise une clef :
| Code: |
pabuisson@gentux ~ $ iwconfig eth1 essid mon-essid
pabuisson@gentux ~ $ iwconfig eth1 mode managed
pabuisson@gentux ~ $ iwconfg eth1 key restricted xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx
Error for wireless request "Set Encode" (8B2A)
SET Failed on device eth1; Operation not supported
|
Malheureusement j'ai l'impression que je peux pas désactiver le cryptage sur ma borne wifi pour tester si ça vient bien de là...
Si quelqu'un a des idées pour me sortir de ce problème, je sèche carrément 
Merci d'avance,
PierreAd |
|
French
