Contributed by phessler on from the two-legs-bad-wireless-good dept.
Reyk Floeter is back with a new daemon, hostapd(8). This new daemon uses IEEE 802.11f to connect wireless Access Points for tracking client associations and movements in large wireless networks, providing roaming improvements. hostapd(8) supports wireless interfaces using 802.11 kernel stack, like ral(4), ath(4), ural(4) and others. It currently does not support the wi(4) driver, since it misses some required functionality.
Future plans include implementing all of 802.11f, and some additional status messages between hostaps.
(Comments are closed)
By Anonymous Coward (139.78.112.166) on
By Jason Houx (216.201.34.104) on
By Venture37 (80.3.64.11) venture37 hotmail on www.geeklan.co.uk
Comments
By phessler (64.173.147.27) on
this is the standard way to mark it.
By Anonymous Coward (213.118.35.44) on
By Justin (64.81.50.82) on
roaming broadcasts are a good thing, but can anyone please enlighten me
as to what other practical features 802.11f has? As far as I know, zero.
This is the primary reason why the standard is being scrapped for
something more practical.
Comments
By reyk (213.23.239.214) on
In addition to a slightly improved roaming capability, IEEE 802.11f is very useful for realtime monitoring of station movements in the ESS. The protocol will be somewhat enhanced with additional and optional information about wireless events on the Host AP side.
The are several reasons for the missing success of IEEE 802.11f. On the one hand, it does have some major design faults (these people didn't know about common operating system concepts) which has been implemented in a compatible but totally different way in hostapd. On the other hand, most of the vendors moved to sell centralized WLAN appliances using the IETF's CAPWAP approach with dumb APs and a "Remote-MAC" (It's always good to sell complex and expensive voodoo boxes...). Personally, I prefer decentralized and redundant network concepts ;).