[FYI] hostapd status

[FYI] hostapd status

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]

Hi,

I just took the time to adjust hostapd to the new nl80211-based hardware
capabilities exporting (patch I recently posted) and it "works" again.

The todo list now pretty much is:

 * bring Michael Wu's "cooked" monitor patches to a suitable shape for
   merging and write iw(1) support for monitor flags; the cooked monitor
   hook shouldn't be in the RX handlers to allow seeing frames that
   other handlers dropped
 * remove 802.1X setting, 802.1X need never be disabled on an AP because
   it can be completely managed by hostapd
 * allow hostapd to set the 'basic' and 'supported' rate sets
 * allow hostapd to set QoS queue parameters
 * allow hostapd to set ERP parameters:
   - RTS/CTS protection
   - preamble
   - slot time
 * make kernel send events via nl80211 (TKIP MMIC, key threshold, ...)
 * make hostapd deal with such kernel events by using libnl properly
   with an ops list
 * implement regulatory domain control kernel/userspace API
 * make hostapd use that API, it wants to be in control of regulatory
   compliance rather than relying on an external daemon

I hope Luis will work on the last two items, and I personally want to
handle only the first two items. All others on the list are up for
grabs.

As usual, patches available from my website (ping me if I forget to push
them.)

I'm fairly confident now that my cfg80211 rate/channel API and the
corresponding nl80211 export code is usable now so I'll post that for
inclusion soon, I'll even rebase it on top of the iwlwifi changes if
they are merged soon enough.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

Re: [FYI] hostapd status

[Luis R. Rodriguez]

On Jan 16, 2008 4:58 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
>
> I just took the time to adjust hostapd to the new nl80211-based hardware
> capabilities exporting (patch I recently posted) and it "works" again.
>
> The todo list now pretty much is:
>
>  * bring Michael Wu's "cooked" monitor patches to a suitable shape for
>    merging and write iw(1) support for monitor flags; the cooked monitor
>    hook shouldn't be in the RX handlers to allow seeing frames that
>    other handlers dropped
>  * remove 802.1X setting, 802.1X need never be disabled on an AP because
>    it can be completely managed by hostapd
>  * allow hostapd to set the 'basic' and 'supported' rate sets
>  * allow hostapd to set QoS queue parameters
>  * allow hostapd to set ERP parameters:
>    - RTS/CTS protection
>    - preamble
>    - slot time
>  * make kernel send events via nl80211 (TKIP MMIC, key threshold, ...)
>  * make hostapd deal with such kernel events by using libnl properly
>    with an ops list
>  * implement regulatory domain control kernel/userspace API
>  * make hostapd use that API, it wants to be in control of regulatory
>    compliance rather than relying on an external daemon

Well we need regulatory daemon of some sort for non-AP hosts. I was
considering throwing this as part of wpa_supplicant/hostapd code. I
guess we'll see.

> I hope Luis will work on the last two items, and I personally want to
> handle only the first two items. All others on the list are up for
> grabs.

ACK -- I will.

  Luis

Re: [FYI] hostapd status

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 656 bytes --]


> Well we need regulatory daemon of some sort for non-AP hosts. I was
> considering throwing this as part of wpa_supplicant/hostapd code. I
> guess we'll see.

That'd be doable, but sort of leaves people who don't want to use
wpa_supplicant out. I guess it's only a matter of time though until we
require use of a supplicant daemon (userspace mlme and all that...) so I
guess it doesn't matter whether we start requiring it now or later...

> > I hope Luis will work on the last two items, and I personally want to
> > handle only the first two items. All others on the list are up for
> > grabs.
> 
> ACK -- I will.

Thanks!

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]