Bug 121913 - madwifi after r1407 doesn't need to create sta mode in rules.d/65-madwifi.rules?
|
Bug#:
121913
|
Product: Gentoo Linux
|
Version: 2005.1
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: mobile@gentoo.org
|
Reported By: cbm@m.fsf.org
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: madwifi after r1407 doesn't need to create sta mode in rules.d/65-madwifi.rules?
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-02-06 17:26 0000
|
After reading this:
http://madwifi.org/wiki/UserDocs/autocreate
I'm not sure we need this line in the udev rules:
KERNEL=="wifi[0-9]*", DRIVER=="ath_pci", ACTION=="add", RUN+="/sbin/wlanconfig
ath create wlandev %k wlanmode sta"
(at least my system seems to work without it.)
We can still provide that 65-madwifi.rules file with the access point
configuration line commented out...
Unconfirmed because I'm not sure I understand this VAP stuff entirely.
For some reason I can no longer assign to mobile@gentoo.org directly (new
bugzilla?) so I CC'd this to mobile@gentoo.org instead.
Correct, the udev rules are no longer needed :)
Fixed in net-wireless/madwifi-{driver,tools}-0.1443.20060207. Thank you for
reporting this.
Oh my. Good to know that the madwifi-ng team is trying to fix the issue for
themselves :)
Just a thought, but maybe a notification that the desired VAP operating mode
can be added to /etc/modules.d/ (as option autocreate=type) could be added to
the ebuild (since iwconfig athX mode does not work).
(In reply to comment #2)
> Just a thought, but maybe a notification that the desired VAP operating mode
> can be added to /etc/modules.d/ (as option autocreate=type) could be added to
> the ebuild (since iwconfig athX mode does not work).
That is considered as basic knowledge. The ebuild already installs the files,
listing the available options.
