Bug 121913

Summary:	madwifi after r1407 doesn't need to create sta mode in rules.d/65-madwifi.rules?
Product:	Gentoo Linux	Reporter:	Colin Macdonald <cbm>
Component:	New packages	Assignee:	Mobile Herd (OBSOLETE) <mobile+disabled>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	High
Version:	2005.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Colin Macdonald 2006-02-06 17:26:50 UTC

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.

Comment 1 Henrik Brix Andersen 2006-02-07 02:27:50 UTC

Correct, the udev rules are no longer needed :)

Fixed in net-wireless/madwifi-{driver,tools}-0.1443.20060207. Thank you for reporting this.

Comment 2 Antti Mäkelä 2006-02-07 05:25:54 UTC

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).

Comment 3 Henrik Brix Andersen 2006-02-07 05:35:50 UTC

(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.