On Mon, 2008-12-29 at 20:23 +0200, Ville Nuorvala wrote: > to my knowledge it is currently the only way to get a realtime > indication that the wireless link quality has changed, please correct > me if I'm wrong. You should be able to obtain information out of nl80211 about the AP you're currently associated with, namely via listing the stations. Currently you can only get rate information, but that's a feature, since the "quality" information "defined" by wext is anything but defined. > Such a feature can be used as an early indication that the link is > going down, and may help prepare a vertical IP layer handover to for > example 3G or just another WLAN interface. The predictive nature of > the event allows you (most of the time) to set up the other link > before the WLAN link is down, which allows a make-before-break > handover without packet loss. In fact such events are described in the > IEEE 802.21 Media Independent Handover document. Ideally these events > might be produced by the 802.11 firmware or at least somewhere lower > in the stack, but lacking that, it can at least be emulated by the > IWSPY interface. Also, as an added bonus for using IWSPY, you can > choose the trigger signal levels yourself and don't have to rely on > any preset levels chosen by the device manufacturer. I really really don't like the iwspy interface, it also requires that you explicitly monitor the AP you're associated to etc. IMHO any such tool needs something that is more reliable and predictable than iwspy. > I'm not bringing any new functionality to the wireless stack, I'm just > reintroducing a feature that got lost when the wireless stack was > changed. For good measure, if you ask me! > Sure a pure netlink interface without any ugly IOCTL hacks would be > nice, but last time I checked the documentation for nl80211 and > cfg80211 was nonexistent, and even driver_nl80211.c straight from the > hostap GIT repository uses WEXT IOCTLs internally for several > different purposes. To me at least it seems like the nl80211 interface > is still far from ready. As my resources are currently very limited, I > don't have time to implement the necessary netlink API and userspace > tools at the moment. The logical conclusion for me was therefore to > just use the old WEXT interface for now. Then can you afford to keep porting the iwspy hack? I really don't want to see this in the tree, especially not since the implementation is ugly too by implementing purely wext stuff in the core mac80211 code. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
