Hello Jeremy,
The current version of madwifi in CVS (Bering-uClibc) is ng r1440, this
includes the recent "autocreate" change.
There are a few ways to setup madwifi, you can set autocreate to none in
/etc/modules like this:
ath_pci autocreate=none
Note- I purposely shut off my config in /etc/interfaces and /etc/modules and
tried to load this module by hand to see what would happen. When I tried
this I get this message-
firewall# insmod wlan
Using /lib/modules/wlan.o
firewall# insmod ath_hal
Using /lib/modules/ath_hal.o
Warning: loading ath_hal will taint the kernel: non-GPL license -
Proprietary
See http://www.tux.org/lkml/#export-tainted for information about tainted
modules
firewall# insmod ath_rate_sample
Using /lib/modules/ath_rate_sample.o
firewall# insmod ath_pci autocreate=none
Using /lib/modules/ath_pci.o
insmod: invalid parameter autocreate
If I do leave the autocreate option on in /etc/modules I can no longer
remotely administer my system. When my system comes up the interface does
not get created (ath0 and wifi0 are missing). Also, shorwall complains
about not being able to route through ath0 (which I would expect). I have
to actually sit at the console to make the changes back and reboot again.
...
This way you can create multiple AP VAPs in /etc/network/interfaces with
"wireless-mode master".
You can also set:
ath_pci autocreate=ap
and don't set "wireless-mode" in /etc/network/interface. An AP VAP will
be
created with module loading.
I also tested it with just "ath_pci" in /etc/modules, so no argument. By
default a STA is created this way. If I set "wireless-mode master" in
/etc/network/interfaces the mode is also changed to "AP".
The best way to setup Madwifi in Bering-uClibc is in MHO the first
option,
so "ath_pci autocreate=none" in /etc/modules and controll the mode in
/etc/network/interfaces.
Eric
Do I have a conflict with the version of modules and packages I am using? I
just downloaded everything last weekend. It looks like the only changes
were a few packages being moved from testing to production. Kel Modderman
suggested the pre-if-up.d script is probably not written to handle the
creation of VAPs. This would appear to be correct (maybe someone can fix
this?). I think if I could get the autocreate option to work I could get my
AP up and running. Thanks all for your help.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/