-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I used wpa_passphase to create the hex number instead of using the ASCII
test and this time it did not balk at it.
However, whether I use proto=WPA or RSN or WPA2, and whether I set the
pairwise=TKIP or uncomment it out, or whether I set the ap_scan=1 or 2
(I think 2 is to scan for hidden SSIDs), the resulting errors are these,
[EMAIL PROTECTED]:/etc# ifup wlan0
WPA: Configuring Interface
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
ioctl[PRISM2_IOCTL_HOSTAPD]: Operation not supported
Failed to set encryption.
The AP is the as reported by iwlist scan,
wlan0 Scan completed :
Cell 01 - Address: 00:1D:8D:A4:7A:3E
ESSID:"removed_for_this_post"
Mode:Master
Frequency:2.412 GHz (Channel 1)
Quality=51/100 Signal level=32/100 Noise level=0/100
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
Simon Lowen wrote:
>
> I installed sed in case this was the problem and the "sed: invalid
> option -- -" went away. Good. However, the rest of the problem persists:
>
>> WPA: Configuring Interface
>> Line 11: Invalid PSK '
>> "11111111111111111111111111111111_00_11111111111111111111111111111111"'.
>> Line 11: failed to parse psk '
>> "11111111111111111111111111111111_00_11111111111111111111111111111111"'.
>> Line 13: WPA-PSK accepted for key management, but no PSK configured.
>> Line 13: failed to parse network block.
>> Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
>> wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
>> FAILED
>
>
>
> Simon Lowen wrote:
>
>
>> Hi all,
>
>> I am trying to setup Angstrom WPA2-TKIP on my hx4700.
>
>> Sed keeps bulking:
>
>> [EMAIL PROTECTED]:/etc$ ifup wlan0
>> sed: invalid option -- -
>> BusyBox v1.2.1 (2007.12.27-19:46+0000) multi-call binary
>
>> Usage: sed [-efinr] pattern [files...]
>
>> WPA: Configuring Interface
>> Line 11: Invalid PSK '
>> "11111111111111111111111111111111_00_11111111111111111111111111111111"'.
>> Line 11: failed to parse psk '
>> "11111111111111111111111111111111_00_11111111111111111111111111111111"'.
>> Line 13: WPA-PSK accepted for key management, but no PSK configured.
>> Line 13: failed to parse network block.
>> Failed to read or parse configuration '/etc/wpa_supplicant.conf'.
>> wpa_supplicant: /usr/sbin/wpa_supplicant daemon failed to start
>> FAILED
>
>> Current /etc/wpa_supplicant.conf reads as,
>> #/etc/wp_supplicant.conf
>> ctrl_interface=/var/run/wpa_supplicant
>> ctrl_interface_group=0
>> eapol_version=1
>> ap_scan=1
>> fast_reauth=1
>> network={
>> ssid="moggy"
>> proto=WPA
>> pairwise=TKIP
>> psk=
>> "11111111111111111111111111111111_00_11111111111111111111111111111111"
>> priority=1
>> }
>
>> I have tried this with and without the double quotes. I presume the
>> problem lies with sed because it is sick at the start, but this may be a
>> red herring.
>
>> The same PSK works fine with my laptop (Debian Ubuntu).
>
>> Any ideas?
>
>> Best wishes, S.
>
>
>
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
- --
PGP plugin for Microsoft Outlook: http://www.gpg4win.org/
PGP plugin for Thunderbird/Mozilla: http://enigmail.mozdev.org
No legitimate reason to know, no legitimate reason to ask.
In the beginning, things were simple. That's arguably because people
were far more stupid, but let's not split hairs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFJMXPRKTaqpMPqlXYRCu28AJ9+ZdYjakVR/2gIBb4wc3VuxoKi+QCggfUo
RoJ3XbGJ+ovULIsSciL7nms=
=BDCJ
-----END PGP SIGNATURE-----
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
