Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: Bas Hulsken <bhulsken@zonnet.nl>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Ron Rindjunsky <ron.rindjunsky@intel.com>
Subject: [FYI] hostapd status
Date: Wed, 16 Jan 2008 22:58:54 +0100	[thread overview]
Message-ID: <1200520735.8007.20.camel@johannes.berg> (raw)

[-- 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 --]

             reply	other threads:[~2008-01-17 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 21:58 Johannes Berg [this message]
2008-01-17 17:52 ` [FYI] hostapd status Luis R. Rodriguez
2008-01-17 23:18   ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1200520735.8007.20.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=bhulsken@zonnet.nl \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=ron.rindjunsky@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox