[Voyage-linux] Wireless setup wiki?
Ian Holm
(spam-protected)
Thu May 7 05:47:46 HKT 2009
I tried running wpa_supplicant without the -Dmadwifi parameter and it gave
me the follwing messages.
ioctl[SIOCSIWMODE]: Invalid argument
Could not configure driver to use managed mode
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-SCAN-RESULTS
.............................................
Why would it try and configure to use managed mode if it's set to Master
mode. Here is my interfaces config.
auto ath0
iface ath0 inet dhcp
# address 10.1.20.1
# netmask 255.255.255.0
# broadcast 10.1.20.255
# #pre-up wlanconfig ath create wlandev wifi1 wlanmode ap
madwifi-base wifi0
wireless-mode Master
# wireless-mode Adhoc
# wireless-mode Managed
up iwpriv ath0 mode 3
up iwconfig ath0 mode master
up iwconfig ath0 essid dd-wrt
up iwconfig ath0 txpower auto
up iwconfig ath0 enc off
up iwconfig ath0 rate auto
# up nat.sh ath0 eth0 "10.1.20.0/24"
On Wed, May 6, 2009 at 2:05 PM, Ian Holm <dxbydt at gmail.com> wrote:
> This is how voyage used to connect pre-0.6.0 afaik. With the release of
> 0.6.0 the madwifi driver was integrated into the kernel. If I try and run
> wpa_supplicant with -Dmadwifi it gives me an error saying madwifi is an
> invalid driver selection. So there has to be some other way that this is
> intended to be setup. One thing I still find odd is that after uncommenting
> those lines in /etc/network/interfaces I get that line on boot that says
> "Failed bringing up ath0" what part of that script is even trying to bring
> up ath0? And why is it failing if I can just run 'ifconfig ath0 up'
> successfully after boot?
>
>
> On Wed, May 6, 2009 at 1:59 PM, Gustin Johnson <gustin at echostar.ca> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Ian Holm wrote:
>> > Alright, details of what I'm trying to do.
>> > I'm using voyage 0.6.1 which is installed on a 1gb CF drive. It's more
>> > or less a clean install with little modification. I have a Gigabyte
>> > GN-WPEAG wireless card that uses one of the supported Atheros drivers,
>> > not sure which one but I've looked it up and verified that it is
>> > supported before.� So far all I've done is uncommented the ath0 block
>> > for madwifi in the /etc/network/interfaces file and changed 'wifi1' to
>> > 'wifi0' in the madwifi-base line. I am trying to use this with DHCP and
>> > WPA-PSK. Since I'm using DHCP, I left the last line in the interfaces
>> > block pertaining to nat.sh commented because I figured that was related
>> > to using a static IP address. I haven't done anything with
>> > /etc/hostapd/hostapd.conf yet and haven't found any documentation on
>> > what changes need to be made there. Your email is the first I've heard
>>
>> hostapd.conf is for setting up as an AP. For a client connect it is not
>> needed.
>>
>> The following is how I connect with my laptop (ubuntu based but the
>> commands should be same):
>>
>> Generate a wpa_supplicant config:
>> wpa_passphrase <essid> <passphrase> > essid.wpa.conf
>>
>> The filename is entirely arbitrary.
>>
>> Then:
>> wpa_supplicant -i ath0 -D madwifi -c essid.wpa.conf
>> Then for dhcp I run: "dhclient ath0"
>>
>> Since my laptop connects to about half a dozen APs in a given day, I do
>> not automate its connection. It only connects when I want it to.
>>
>>
>> You should note that I did not use the flag to run wpa_supplicant in the
>> background because I like to see the output. If you are connecting to
>> your voyage box via serial, then you probably want to add the "-B" flag
>> or use wpa_cli.
>>
>> As always, the "man" command is your friend.
>>
>> Hth,
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkoB+hIACgkQwRXgH3rKGfP+hgCfQtNthLJjfV6BBw2RwV/57TrE
>> vrMAoJPq2+nvy11v/wZWWc4lfvLfN7zQ
>> =66+R
>> -----END PGP SIGNATURE-----
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20090506/6ec7e744/attachment.html>
More information about the Voyage-linux
mailing list