Re: nl80211 status? (implying cfg80211 status)

[David Lamparter <lists@diac24.net>]

Hooray, message crossing :)

> What I'd do if I had time now is add things to nl80211/cfg80211 and then
> implement the calls in mac80211 (or a fullmac driver of your choice.)
> Then write the appropriate userspace tool for testing and see if it
> works, i.e. you can associate, do key operations etc. Use WEP for now,
> and then maybe modify wpa_supplicant too for nl80211. Then, at some
> point, you have wpa_supplicant working on mac80211 (or the driver). Then
> in theory you don't need wext any more, and as an afterthought you can
> still add wext compatibility so the deprecated wireless tools continue
> to work.

Yeah, I agree. Guess I overshooted a bit on converting wext. For the
userspace part I started by adding some genetlink helper functions to
iproute2, will try to get them upstream later. (tomorrow)

I'm hoping to add an "ip wireless" part, since iproute2 already has all the
netlink stuff and I really like its syntax. I rudimentarily started hacking
it up, which is why I noticed there's no PHY configuration command.

For the kernel part, if I were to work on it, I'd be adding it to mac80211.
The only 802.11 devices I own are a laptop with a rt2500 and a WRT router,
and developing for that router isn't that fun.


David

---

[equinox@neptune]:~/src/iproute2/ip # ./ip w
0: phy0
RTNETLINK answers: Operation not supported
    6: wlan0: association status unknown
RTNETLINK answers: Operation not supported
    5: wmaster0: association status unknown