https://bugzilla.novell.com/show_bug.cgi?id=329280
User jg@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=329280#c12
Joachim Gleissner changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zoz@novell.com
Status|ASSIGNED |NEEDINFO
Info Provider| |mt@novell.com
--- Comment #12 from Joachim Gleissner 2007-12-07 08:45:24 MST ---
It is indeed not a rt2x00 driver problem. The new wireless stack mac80211,
which rt2x00 uses, behaves differently from how wireless LAN drivers used to.
Before mac80211, drivers began to scan for a suitable access point as soon as
their interface was set up, and possibly even tried to associate. mac80211 does
expect a bit more initiative from user space. The Wireless Extensions do not
define some "start" command, people used to consider setting the ESSID as kind
of implicit start command. mac80211 seems to rather consider setting the AP
address so (manual scan works as well, obviously). Well, changing ifup-wireless
to explicitly set the AP address is no big deal, in fact it fixes a bug, as it
did not care about AP settings at all before (seems nobody noticed so far).
Having to set up the link in ifup-wireless is a bit awkward, but I do not think
it will do any harm. Marius, do you have objections against this?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.