Punky
My wpa_psk file is of the form:-
00:00:00:00:00:00 [63 hex characters]
and was created by:-
wpa_passphrase myssid password /etc/hostapd/wpa_psk
and then editing the resultant file to add the leading 00:... and remove
everything else. I have checked that I didn't accidentally change
Punky
This page, however:-
http://kbserver.netgear.com/kb_web_files/n101190.asp
suggests otherwise!
I'll try the wpa_supplicant alternative when I get back tonight.
Regards
Robin
Kim-man 'Punky' Tse said:
Hi Robin,
Not sure if I am wrong, but I wonder WPA is supported in Win98SE.
Punky
I'd seen the exchange to which you referred me, but had understood that the
hostapd version you uploaded was the version I had; dpkg --list hostapd
shows version number 0.5.2-1 installed. I had downloaded voyage 0.2. I
attempted to update hostapd from the 0.2 repository, but apt-get
Punky
I've tried it; no help, I'm afraid; a chunk of the output following my attempt
to connect follows (it seems to repeat, albeit not after the same number of
repeats each time):-
Wireless event: cmd=0x8c03 len=20
ath0: STA 00:0f:b5:ae:a0:18 IEEE 802.11: associated
New STA
ath0: STA
Hi Robin,
The debug message shows the authentication failed at very early stage.
Last hope: Are you sure you set the right things in wpa_psk_file? I
would suggest that you test with wpa_passphrase parameter first, didn't you?
for wpa_psk_file, you can see the example in:
My WAP hardware is:-
Soekris 4521-30 with a Gigabyte GN-WIAG01 mini-PCI card (Atheros 5212
(5004XR) chipset).
I have installed Voyage 0.2 with the latest (from the 0.2 repository)
versions of madwifi and hostapd.
I am connecting from a ThinkPad A22m running Win98SE using a Netgear WG511T
PC
Hi Robin,
I have encountered the same before 0.2 was released. You may need to
make hostapd to use the EAP_VERSION=1. And the stock voyage-0.2 is able
to support it. Please read the following thread for this issue.
http://www.mail-archive.com/voyage-linux@list.voyage.hk/msg00504.html
