Brooks Davis wrote:
On Sun, Apr 20, 2008 at 01:54:26PM -0700, Sam Leffler wrote:
Expect fallout from these changes. Known issues:
o kernel configs must be updated to remove wlan_scan_*
o ipw is broken
o wi works for Prism cards with newer firmware (1.7.x tested w/ wpa!) but
older cards/firmware and Lucent cards are known broken
o adhoc mode is little tested and may be broken
o monitor mode radiotap support is available only on the "parent device"
I promise to look at ipw but it won't happen immediately so anyone that's
affected should feel free to dig in. I have no plans to touch wi; folks
that persist in using these cards should fix issues now that I've rewritten
the driver so that it is more properly integrated with net80211. OTOH wi
now does wpa and adding wds support should be straightforward.
Also, the required rc.conf options have changed and are mostly
incompatible. The infrastructure is subject to change, but it's the
best I've been able to come up with so far. Some sort of transition
tool might be in order.
If you the following in your rc.conf file:
ifconfig_ath0="DHCP WPA"
you should change it to:
vaps_ath0="wlan0" # Any name will work
ifconfig_wlan0="DHCP WPA" # Also change any other ath0 related
# variables...
You if you wanted a more informative naming scheme you could do
something like:
vaps_ath0="ath0.sta"
ifconfig_ath0_sta="DHCP WPA"
Note that wlan-aware tools default to wlan0 (e.g. wlandebug, wlanstats)
so using "informative naming" will require extra typing. We are in need
of a lib80211 or similar and if/when that happens it'd be good to have a
routine that finds the most likely default network interface; e.g. by
scanning for wlanX interfaces that are cloned from an 802.11 interface.
Sam
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
