[Voyage-linux] Wireless setup wiki?
Ian Holm
(spam-protected)
Thu May 7 07:54:50 HKT 2009
I tried running 'ifup ath0 -v' and here is output:
voyage:~# ifup ath0 -v
Configuring interface ath0=ath0 (inet)
run-parts --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/050madwifi
ath0
run-parts: executing /etc/network/if-pre-up.d/bridge
run-parts: executing /etc/network/if-pre-up.d/hostap-utils
run-parts: executing /etc/network/if-pre-up.d/hostapd
run-parts: executing /etc/network/if-pre-up.d/ifenslave
run-parts: executing /etc/network/if-pre-up.d/vlan
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: terminating wpa_supplicant daemon via pidfile
/var/run/wpa_supplicant.ath0.pid
Stopped /sbin/wpa_supplicant (pid 4186).
wpa_supplicant: removing
/lib/init/rw/sendsigs.omit.d/wpa_supplicant.wpa_supplicant.ath0.pid
wpa_supplicant: using default driver type: wpa-driver wext
wpa_supplicant: /sbin/wpa_supplicant -B -P /var/run/wpa_supplicant.ath0.pid
-i ath0 -D wext -q -f /var/log/wpa_supplicant.ath0.log -c
/etc/wpa_supplicant/wpa_supplicant.conf -C /var/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile:
/lib/init/rw/sendsigs.omit.d/wpa_supplicant.wpa_supplicant.ath0.pid
wpa_supplicant: ctrl_interface socket located at
/var/run/wpa_supplicant/ath0
pump -i ath0
Operation failed.
Failed to bring up ath0.
So after everything i've tried I still don't seem to be any closer. Could it
likely be my hardware? Is there another way to do this? Some sort of kernel
module I could compile? I'm willing to do anything, I just have to get
wireless working soon here for a project I'm working on. I'd be satisfied
with a workaround as long as I accomplish connecting to a standard WPA-PSK
encrypted wireless router.
On Wed, May 6, 2009 at 3:44 PM, Ian Holm <dxbydt at gmail.com> wrote:
> So I tried setting it to managed mode and then running 'wpa_supplicant
> -iath0 -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext and it didn't give
> me the same error as before but it still complains about the link being
> down. I did 'ip link set ath0 up' and ran wpa_supplicant again but it still
> failed. I also tried 'ifup ath0' and it seems that's the script that's
> creating the message:
>
> Operation not permitted
> Failed bringing up ath0
>
> Am I missing some kind of step here?
>
> On Wed, May 6, 2009 at 3:02 PM, Gustin Johnson <gustin at echostar.ca> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Ian Holm wrote:
>> > I tried running wpa_supplicant without the -Dmadwifi parameter and it
>> > gave me the follwing messages.
>>
>> There are other options, like -D wext.
>> >
>> > Why would it try and configure to use managed mode if it's set to Master
>> >
>> Master mode is for APs, you want managed. Wpa_supplicant is for devices
>> in Managed mode. Hostap is for master.
>>
>> > mode. Here is my interfaces config.
>>
>> Ignore this for a little while.
>>
>> Try getting it to bind manually using the instructions I previously
>> supplied before messing around in /etc/network/interfaces. This means
>> ignore the ifup/ifdown scripts for now.
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkoCCP0ACgkQwRXgH3rKGfMyfQCcDHMmr2QTLNgpNJtuAXYEEWaL
>> rYkAnjjwNb725aebgNQ35oKY6tNFJPpj
>> =vlWU
>> -----END PGP SIGNATURE-----
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20090506/265a2b64/attachment.html>
More information about the Voyage-linux
mailing list