I've been working on this all morning, but can't resolve this problem...
My system has been running fine for several days, I can log in locally or over the wan using SSH without a problem. However I need to shift the unit to a spot without a lan socket, so I need to set up wifi.
I have purchased a Netgear G54/N150 wireless USB adapter (based on reported compatibility here
http://forum.tinycorelinux.net/index.php/topic,12910.msg73164.html#msg73164I am running Core in text mode only - no GUI. Router is an oldish Dlink DI-624+ using WPA-PSK authentication, which is working fine with the windows wired and wireless clients connected to it.
As per the WIKI, I have installed:
wireless_tools.tcz
wireless-3.0.21-tinycore.tcz
firmware.tcz
wpa-supplicant.tcz
iwconfig sees the interface
tc@box:~$ iwconfig
lo no wireless extensions.
dummy0 no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Power Management:on
I've configured /opt/wpa_configure.conf as follows
tc@box:~$ cat /opt/wpa_configure.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="myssid"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk="mypassword"
}
I ran filetool.sh -b after saving it. Note: I originally had the full psk key in there, and changed to a text passphrase (as per wpa_supplicant man page), but no difference to results. I have checked and double checked the passphrase. It must be right anyway as it connects eventually (see below).
Starting wpa_suplicant gets this:
tc@box:~$ sudo wpa_supplicant -i wlan0 -c /opt/wpa_configure.conf &
tc@box:~$ wlan0: Trying to associate with 00:11:95:0e:92:aa (SSID='mySSID' freq=2437 MHz)
wlan0: Associated with 00:11:95:0e:92:aa
wlan0: Michael MIC failure detected
wlan0: WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99)
wlan0: Michael MIC failure detected
wlan0: WPA: Sending EAPOL-Key Request (error=1 pairwise=1 ptk_set=1 len=99)
wlan0: TKIP countermeasures started
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
wlan0: Trying to associate with 00:11:95:0e:92:aa (SSID='mySSID' freq=2437 MHz)
wlan0: Associated with 00:11:95:0e:92:aa
wlan0: WPA: Countermeasures - dropped EAPOL packet
wlan0: WPA: Countermeasures - dropped EAPOL packet
wlan0: WPA: Countermeasures - dropped EAPOL packet
wlan0: WPA: Countermeasures - dropped EAPOL packet
wlan0: CTRL-EVENT-DISCONNECTED bssid=00:11:95:0e:92:aa reason=0
which loops though several times, taking about 10-15 minutes to connect.
Once connected I get this:
tc@box:~$ iwconfig
lo no wireless extensions.
dummy0 no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:"mySSID"
Mode:Managed Frequency:2.437 GHz Access Point: 00:11:95:0E:92:AA
Bit Rate=54 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
Link Quality=34/70 Signal level=-76 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:26 Missed beacon:0
Then running udhcpc returns this:
tc@box:~$ sudo udhcpc -i wlan0
udhcpc (v1.19.4) started
Sending discover...
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.104...
Sending select for 192.168.0.104...
Sending select for 192.168.0.104...
Which also repeats several times, before giving me an IP address and hence a working wifi connection.
The end result is it takes 20 minutes or more to connect to the router. Any ideas what to change to make this useable?
Also, whenever I reboot (with the wifi adapter and lan cable plugged in), I can't SSH back in (on either eth0 or wlan0). I have to do a hard reset to get SSH access again. Since all configuration is via SSH this is painful, any ideas why this might be happening?