| View previous topic :: View next topic |
| Author |
Message |
Shopro
l33t
Joined: 12 May 2004
Posts: 678
Location: Dayton, OH, USA
|
 Posted: Fri Nov 03, 2006 10:42 pm Post subject: ipw3945 and wpa_supplicant problems. |
 |
|
For whatever reason it seems to go into a loop.
/etc/wpa_supplicant/wpa_supplicant.conf
| Code: | ctrl_interface=/var/run/wpa_supplicant
#ctrl_interface_group=0
#eapol_version=1
#ap_scan=2
#fast_reauth=1
#network={
ap_scan=0
update_config=1
eapol_version=2
network={
scan_ssid=1
ssid="NETGEAR"
#proto=WPA
#key_mgmt=WPA-PSK
#pairwise=TKIP
#group=TKIP
psk="removedhere"
#priority=2
}
|
wpa_supplicant -dd -ieth1 -c /etc/wpa_supplicant/wpa_supplicant.conf -Dwext
| Code: | Initializing interface 'eth1' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ap_scan=0
update_config=1
eapol_version=2
Line: 13 - start of a new network block
scan_ssid=1 (0x1)
ssid - hexdump_ascii(len=7):
4e 45 54 47 45 41 52 NETGEAR
PSK (ASCII passphrase) - hexdump_ascii(len=8): [REMOVED]
PSK (from passphrase) - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='NETGEAR'
Initializing interface (2) 'eth1'
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)=20 WE(source)=16 enc_capa=0xf
capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:18:de:34:d1:d8
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface eth1
RTM_NEWLINK: operstate=0 ifi_flags=0x1022 ()
Wireless event: cmd=0x8b06 len=8
RTM_NEWLINK: operstate=0 ifi_flags=0x11063 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11063 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
RTM_NEWLINK: operstate=0 ifi_flags=0x11023 ([UP][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'eth1' added
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
BSSID not set when trying to send an EAPOL frame
Using the source address of the last received EAPOL frame 00:00:00:00:00:00 as the EAPOL destination
TX EAPOL - hexdump(len=4): 02 01 00 00
Authentication with 00:00:00:00:00:00 timed out.
Added BSSID 00:00:00:00:00:00 into blacklist
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
Setting scan request: 0 sec 0 usec
EAPOL: External notification - portControl=Auto
Already associated with a configured network - generating associated event
Association info event
State: DISCONNECTED -> ASSOCIATED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
Associated with 00:00:00:00:00:00
WPA: Association event - clear replay counter
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
EAPOL: External notification - portEnabled=1
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: SUPP_BE entering state IDLE
Setting authentication timeout: 10 sec 0 usec
Cancelling scan request
EAPOL: startWhen --> 0
EAPOL: SUPP_PAE entering state CONNECTING
EAPOL: txStart
BSSID not set when trying to send an EAPOL frame
Using the source address of the last received EAPOL frame 00:00:00:00:00:00 as the EAPOL destination
TX EAPOL - hexdump(len=4): 02 01 00 00
CTRL-EVENT-TERMINATING - signal 2 received
Removing interface eth1
State: ASSOCIATED -> DISCONNECTED
wpa_driver_wext_set_operstate: operstate 0->0 (DORMANT)
WEXT: Operstate: linkmode=-1, operstate=5
No keys have been configured - skip key clearing
EAPOL: External notification - portEnabled=0
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: SUPP_BE entering state INITIALIZE
EAPOL: External notification - portValid=0
wpa_driver_wext_set_wpa
wpa_driver_wext_set_drop_unencrypted
wpa_driver_wext_set_countermeasures
No keys have been configured - skip key clearing
WEXT: Operstate: linkmode=0, operstate=6
Removed BSSID 00:00:00:00:00:00 from blacklist (clear)
Cancelling scan request
|
_________________
Just because I have nothing to say is no reason why you shouldn't listen. |
|
| Back to top |
|
 |
madisonicus
Veteran
Joined: 20 Sep 2006
Posts: 1130
|
| Posted: Sat Nov 04, 2006 2:27 am Post subject: |
|
|
Looks like either the psk is incorrect, being transmitted incorrectly (ascii/hex), or possibly the router is not set to allow the mac address of your card. That would explain the association and then disconnection.
Double check your mac filtering and your psk. Might also try a very brief non-encrypted connection with your wireless router just to make sure that works without the encryption.
The wpa_gui does a good job of picking the correct settings. It might help to use it to figure out what it thinks you should be using.
I've heard that sometimes the psk will work better if you convert it to hex first.
HTH,
m
_________________
Please add [SOLVED] to your message title if you feel that your question has been answered.
------
Intel Q9300 Core2 Quad * Gigabyte GA-EP35C-DS3R
Samsung x360
AMD64 x2 4200+ * TF7050-M2 * HTPC
ZOTAC ION A-U Mini-ITX * HTPC |
|
| Back to top |
|
|
Shopro
l33t
Joined: 12 May 2004
Posts: 678
Location: Dayton, OH, USA
|
| Posted: Sat Nov 04, 2006 3:19 am Post subject: |
|
|
Yes it works correctly without any encryption, but I would really like to use it with wpa only, as I know there are at least a dozen of other wireless networks in my building. And don't really want them to be using my network. My wireless router only allows these:
| Quote: | WPA-PSK (Wi-Fi Protected Access Pre-Shared Key)
Passphrase: (8-63 characters)
Key Lifetime: (minutes) |
_________________
Just because I have nothing to say is no reason why you shouldn't listen. |
|
| Back to top |
|
|
Shopro
l33t
Joined: 12 May 2004
Posts: 678
Location: Dayton, OH, USA
|
| Posted: Sat Nov 04, 2006 3:25 am Post subject: |
|
|
Forgot this one.
# /etc/init.d/net.eth1 start
| Code: | ioctl[SIOCSIWMODE]: Resource temporarily unavailable
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily unavailable [ ok ]th param 5 value 0x1 -
* Starting wpa_cli on eth1 ... [ ok ]
* Backgrounding ... |
_________________
Just because I have nothing to say is no reason why you shouldn't listen. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
