View previous topic :: View next topic |
Author |
Message |
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
Posted: Fri Jan 05, 2007 5:07 pm Post subject: WPA - Netgear ma401 - Not working [solved] |
|
|
I am trying to install WPA for my netgear ma401. It gives me this message:
* Service net.eth1 starting
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Operation not supported
ioctl[SIOCSIWENCODE]: Invalid argument
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 5 value 0x1 - * WARNING: net.eth1 has started but is inactive
Now I found a document on the internet that says I cannot use a orinoco driver with WPA.
In dmesg I see :
[ 6.657000] eth1: Hardware identity 800c:0000:0001:0000
[ 6.657000] eth1: Station identity 001f:0006:0001:0003
[ 6.657000] eth1: Firmware determined as Intersil 1.3.6
[ 6.657000] eth1: Ad-hoc demo mode supported
[ 6.657000] eth1: IEEE standard IBSS ad-hoc mode supported
[ 6.657000] eth1: WEP supported, 104-bit key
[ 6.657000] eth1: MAC address 00:11:22:33:44:55
[ 6.657000] eth1: Station name "Prism I"
[ 6.658000] eth1: ready
[ 6.658000] eth1: orinoco_cs at 1.0, irq 11, io 0x2100-0x213f
orinoco_cs, that means it's using orinoco driver?
But, when I compiled my kernel, I had selected Hermes (not orinoco).
Is Hermes really Orinoco? If that's the case, than what Kernel options do I need to make my setup work?
Thanks,
David
Last edited by dlublink on Tue Feb 06, 2007 12:32 am; edited 1 time in total |
|
Back to top |
|
|
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
Posted: Fri Jan 05, 2007 5:31 pm Post subject: |
|
|
I did some further research and it was suggested that I use the Host AP drivers:
<*> IEEE 802.11 for Host AP (Prism2/2.5/3 and WEP/TKIP/CCMP)
[ ] Support downloading firmware images with Host AP driver
< > Host AP driver for Prism2/2.5/3 in PLX9052 PCI adaptors
< > Host AP driver for Prism2.5 PCI adaptors
<*> Host AP driver for Prism2/2.5/3 PC Cards
But I am not sure this is correct, because without WPA_SUPPLICANT enabled in conf.d/net (modules=wpa_supplicant). It gives this error (network on WEP):
compaq david # /etc/init.d/net.eth1 restart
* Caching service dependencies ... [ ok ]
* Service net.eth1 stopping
* Service net.eth1 stopped
* Service net.eth1 starting
Error, dhcpStart: interface eth1 is not Ethernet or 802.2 Token Ring
[ !! ]
* ERROR: net.eth1 failed to start
With WPA active on the router and wpa_supplicant enabled in conf.d/net I get this:
compaq conf.d # /etc/init.d/net.eth1 restart
* Caching service dependencies ... [ ok ]
* Service net.eth1 stopping
* Service net.eth1 stopped
* Service net.eth1 starting
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 7 value 0x1 - * WARNING: net.eth1 has started but is inactive
So with this upgrade, not only am I not able to connect to WPA, but I can no longer connect with WEP.
Thoughts?
David |
|
Back to top |
|
|
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
Posted: Fri Jan 05, 2007 5:32 pm Post subject: |
|
|
Some more information from dmesg:
compaq conf.d # dmesg | grep host
[ 20.049712] hostap_cs: 0.4.4-kernel (Jouni Malinen <jkmaline@cc.hut.fi>)
[ 6.311000] hostap_cs: setting Vcc=33 (constant)
[ 6.311000] hostap_cs: Registered netdevice wifi0
[ 6.351000] hostap_cs: index 0x01: , irq 11, io 0x2100-0x213f
[ 6.652000] wifi0: defaulting to host-based encryption as a workaround for firmware bug in Host AP mode WEP |
|
Back to top |
|
|
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
Posted: Fri Jan 05, 2007 5:35 pm Post subject: |
|
|
Hmm,
I think I may have misunderstood Host AP. It looks like Host AP is to be the access point, not a computer on the network. (correct me if I am wrong).
David |
|
Back to top |
|
|
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
Posted: Fri Jan 05, 2007 5:57 pm Post subject: |
|
|
[quote="dlublink"]Hmm,
I think I may have misunderstood Host AP. It looks like Host AP is to be the access point, not a computer on the network. (correct me if I am wrong).
David[/quote]
Alright, I am back to my original drivers. WEP is table, but I am unable to work with WPA.
Anyone have any ideas?
Thanks,
David |
|
Back to top |
|
|
dlublink Tux's lil' helper
Joined: 30 Sep 2006 Posts: 146
|
|
Back to top |
|
|
|