linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 2/2] mac80211: revamp interface and filter configuration
Date: Tue, 21 Aug 2007 23:14:14 +0200	[thread overview]
Message-ID: <200708212314.15010.IvDoorn@gmail.com> (raw)
In-Reply-To: <20070821161942.938977000@sipsolutions.net>

On Tuesday 21 August 2007, Johannes Berg wrote:
> Drivers are currently supposed to keep track of monitor
> interfaces if they allow so-called "hard" monitor, and
> they are also supposed to keep track of multicast etc.
> 
> This patch changes that, replaces the set_multicast_list()
> callback with a new configure_filter() callback that takes
> filter flags (FIF_*) instead of interface flags (IFF_*).
> For a driver, this means it should open the filter as much
> as necessary to get all frames according to the filter flags.
> 
> Multicast filtering is a bit special, which is why drivers
> that do not require FIF_ALLMULTI for multicast address filters
> (i.e. they actually have filters for multicast addresses)
> need to set the new IEEE80211_HW_MULTICAST_FILTER flag and
> call the ieee80211_get_mc_list_item() function.
> 
> At the same time, drivers are no longer notified about
> monitor interfaces at all, this means they now need to
> implement the start() and stop() callbacks and the new
> change_filter_flags() callback. Also, the start()/stop()
> ordering changed, start() is now called *before* any
> add_interface() as it really should be, and stop() after
> any remove_interface().
> 
> The patch also changes the behaviour of setting the bssid
> to multicast for scanning when IEEE80211_HW_NO_PROBE_FILTERING
> is set; the IEEE80211_HW_NO_PROBE_FILTERING flag is removed
> and the filter flag FIF_BCN_PRBRESP_PROMISC introduced.
> This is a lot more efficient for hardware like b43 that
> supports it and other hardware can still set the BSSID
> to multicast.

Personally I like the idea of this packet filtering, implementation
and driver interface looks allright to me.

> WARNING: This patch makes the ralink drivers BUG_ON().

If you can give me a warning when you are going to submit this
for inclusion, I'll cook up a patch to make it work for rt2x00. :)

Ivo

  reply	other threads:[~2007-08-21 21:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 16:18 [RFC 0/2] the filter stuff again Johannes Berg
2007-08-21 16:18 ` [RFC 1/2] mac80211: allow drivers to indicate failed FCS/PLCP checksum Johannes Berg
2007-08-21 21:07   ` Ivo van Doorn
2007-08-22  9:22     ` Johannes Berg
2007-08-22 19:11       ` Ivo van Doorn
2007-08-23 14:13         ` Johannes Berg
2007-08-21 16:18 ` [RFC 2/2] mac80211: revamp interface and filter configuration Johannes Berg
2007-08-21 21:14   ` Ivo van Doorn [this message]
2007-08-22  9:23     ` Johannes Berg
2007-09-03  2:07   ` Daniel Drake
2007-09-03  8:36     ` Johannes Berg
2007-09-03  9:29     ` Johannes Berg
2007-09-03 10:57       ` Johannes Berg
2007-09-05  5:16         ` Ulrich Kunitz
2007-09-05 11:23           ` Johannes Berg
2007-09-05 14:16             ` Michael Buesch
2007-09-05 14:21               ` Johannes Berg
2007-09-05 14:23             ` Michael Wu
2007-09-05 14:33               ` Johannes Berg
2007-09-03 13:32       ` Johannes Berg
  -- strict thread matches above, loose matches on Subject: below --
2007-08-15 15:25 [RFC 0/2] device configuration changes Johannes Berg
2007-08-15 15:25 ` [RFC 2/2] mac80211: revamp interface and filter configuration Johannes Berg
2007-08-16 12:41   ` 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=200708212314.15010.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).