|
|
|
|
||||||
| linux.debian.user debian-user@lists.debian.org. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Dear debianners,
I have a 3com OfficeConnect wireless router, which is running in 802.11g mode. I have a Sony Vaio notebook, with a Intel PRO/Wireless 2200BG network controller, which appears in the system as "eth2". I have configured everything, with the of this list, in order to have the wireless network running without encryption. Without encryption, the wireless network is running fine. My problem is with encryption. In the router side, I have configured things to use WPA-PSK with TKIP encryption. In the notebook side, I have installed wpa_supplicant and created the corresponding /etc/wpa_supplicant.conf file, which reads as follows: # # File: wpa_supplicant.conf # ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=root network={ ssid="myhomenet" scan_ssid=1 key_mgmt=WPA-PSK psk="secretphrase" } the ssid and psk are the same defined in the router. Now, when a try to access the encrypted network with wpa_supplicant, I have the following error: marcelo@tango:~$ sudo wpa_supplicant -ieth2 -c/etc/wpa_supplicant.conf -d -B Initializing interface 'eth2' conf '/etc/wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group='root' (DEPRECATED) Priority group 0 id=0 ssid='myhomenet' Initializing interface (2) 'eth2' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf capabilities: key_mgmt 0xf enc 0xf WEXT: Operstate: linkmode=1, operstate=5 Own MAC address: 00:0e:35:01:a8:73 wpa_driver_hostap_set_wpa: enabled=1 wpa_driver_hostap_set_key: alg=none key_idx=0 set_tx=0 seq_len=0 key_len=0 ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported Failed to set encryption. wpa_driver_hostap_set_key: alg=none key_idx=1 set_tx=0 seq_len=0 key_len=0 ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported Failed to set encryption. wpa_driver_hostap_set_key: alg=none key_idx=2 set_tx=0 seq_len=0 key_len=0 ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported Failed to set encryption. wpa_driver_hostap_set_key: alg=none key_idx=3 set_tx=0 seq_len=0 key_len=0 ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported Failed to set encryption. wpa_driver_hostap_set_countermeasures: enabled=0 wpa_driver_hostap_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec ctrl_interface_group=0 (from group name 'root') Added interface eth2 Daemonize.. and I am unable to reach the wireless router. I have search the archives and googled the web, but the information doesn't . I would appreciate very much any hint regarding this problem. Thanks in advance, regards Marcelo -- Marcelo Chiapparini chiappa@oi.com.br -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
The problem with WPA is the vendors sometimes implement it in their own way. That is why there a lot incompatibility issues with it. Why not just use WEP? I am sure it offers a good enough level of encryption for your needs. Sorry I am not of much more . Amit -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
On Wed, 30 Jan 2008 14:48:37 -0200
Marcelo Chiapparini <chiappa@oi.com.br> wrote: > My problem is with encryption (WPA). This is what I have: /etc/network/interfaces (relevant lines to wireless link only): #DHCP doesn't work very well with wpa here, so I use static #addresses. Also, it's a way of taking out the equation some #variables. iface eth2 inet static address 192.168.11.3 #my address netmask 255.255.255.0 gateway 192.168.11.1 #my router's address wireless-essid "my ssid" up wpa_supplicant -ieth2 -c/etc/wpa_supplicant.conf -Bw -Dwext down killall wpa_supplicant allow-hotplug eth2 My wpa_supplicant.conf is just the output of wpa_passphrase (man wpa_passphrase). Run it with your ssid and passphrase and copy the output to wpa_supplicant.conf, so it looks like this: /etc/wpa_supplicant.conf: network={ ssid="my ssid" #psk="whatevercrossesyourmindthebiggerthebetter" psk=bigstringoflettersandnumbersgeneratedbasedonyo urpassphraseandssid } Put the psk (the second and real one) in your router's settings. That should be it. Check that you can get authentification from the router by running wpa_supplicant like this: wpa_supplicant -ieth2 -c/etc/wpa_supplicant.conf -Dwext -d Once you convince yourself that it can connect to the router kill it and bring your interface up the usual way. I hope it works for you. -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
On Wed, 2008-01-30 at 17:29 -0800, Amit Uttamchandani wrote:
> The problem with WPA is the vendors sometimes implement it in their own way. That is why there a lot incompatibility issues with it. > > Why not just use WEP? I am sure it offers a good enough level of encryption for your needs. > > Sorry I am not of much more . > > Amit Amit, thank you very much for your suggestion. I tried WEP and it works fine. I am running WEP then in the meantime until solve the WAP problem. Regards Marcelo -- Marcelo Chiapparini chiappa@oi.com.br -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
On Thu, 2008-01-31 at 11:34 +0000, Jose Rodriguez wrote:
> On Wed, 30 Jan 2008 14:48:37 -0200 > Marcelo Chiapparini <chiappa@oi.com.br> wrote: > > > My problem is with encryption (WPA). > > This is what I have: > > /etc/network/interfaces (relevant lines to wireless link only): > > #DHCP doesn't work very well with wpa here, so I use static > #addresses. Also, it's a way of taking out the equation some > #variables. > iface eth2 inet static > address 192.168.11.3 #my address > netmask 255.255.255.0 > gateway 192.168.11.1 #my router's address > > wireless-essid "my ssid" > up wpa_supplicant -ieth2 -c/etc/wpa_supplicant.conf -Bw -Dwext > down killall wpa_supplicant > allow-hotplug eth2 > > > My wpa_supplicant.conf is just the output of wpa_passphrase (man > wpa_passphrase). Run it with your ssid and passphrase and copy the > output to wpa_supplicant.conf, so it looks like this: > > /etc/wpa_supplicant.conf: > > network={ > ssid="my ssid" > #psk="whatevercrossesyourmindthebiggerthebetter" > psk=bigstringoflettersandnumbersgeneratedbasedonyo urpassphraseandssid > } > > > Put the psk (the second and real one) in your router's settings. > That should be it. Check that you can get authentification from > the router by running wpa_supplicant like this: > > wpa_supplicant -ieth2 -c/etc/wpa_supplicant.conf -Dwext -d > > Once you convince yourself that it can connect to the router kill > it and bring your interface up the usual way. > > I hope it works for you. Jose, thank you very much for your suggestion. I will try the static address method and let you know. Regards Marcelo -- Marcelo Chiapparini chiappa@oi.com.br -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org |
|
![]() |
| Outils de la discussion | |
|
|