All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Daniel Drake <dsd@gentoo.org>,
	linux-wireless@vger.kernel.org, jbenc@suse.cz,
	Michael Buesch <mb@bu3sch.de>,
	Bcm43xx-dev@lists.berlios.de,
	Larry Finger <larry.finger@lwfinger.net>
Subject: Re: mac80211 IPv6 problems
Date: Mon, 6 Aug 2007 13:05:00 -0400	[thread overview]
Message-ID: <20070806170500.GE6442@tuxdriver.com> (raw)
In-Reply-To: <200708030102.17358.flamingice@sourmilk.net>

On Fri, Aug 03, 2007 at 01:02:12AM -0700, Michael Wu wrote:

> This doesn't seem quite right. I think ieee80211_rx_h_data is a safer place 
> for this check (inside the IEEE80211_FCTL_FROMDS case), and allows various 
> statistics to be updated. ieee80211_rx_h_sta_process is another function that 
> might work though that would probably involve more code to add all the right 
> checks.

The patch below seems to work for me w/ an otherwise stock F-7 kernel
w/ iwl3945.  Thoughts?

From: John W. Linville <linville@tuxdriver.com>

[PATCH] mac80211: filter locally-originated multicast frames

In STA mode, the AP will echo our traffic.  This includes multicast
traffice.

Receiving these frames confuses some protocols and applications,
notably IPv6 Duplicate Address Detection.

Signed-off-by: John W. Linville <linville@tuxdriver.com>
---

 net/mac80211/ieee80211.c |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/net/mac80211/ieee80211.c b/net/mac80211/ieee80211.c
index a42e70e..0097b0a 100644
--- a/net/mac80211/ieee80211.c
+++ b/net/mac80211/ieee80211.c
@@ -3030,9 +3030,10 @@ ieee80211_rx_h_data(struct ieee80211_txrx_data *rx)
 		memcpy(dst, hdr->addr1, ETH_ALEN);
 		memcpy(src, hdr->addr3, ETH_ALEN);
 
-		if (sdata->type != IEEE80211_IF_TYPE_STA) {
+		if (sdata->type != IEEE80211_IF_TYPE_STA ||
+		    (is_multicast_ether_addr(dst) &&
+		     !compare_ether_addr(src, dev->dev_addr)))
 			return TXRX_DROP;
-		}
 		break;
 	case 0:
 		/* DA SA BSSID */


-- 
John W. Linville
linville@tuxdriver.com

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 15:53 [RFC 0/10] Port of bcm43xx from softmac to mac80211 Larry Finger
2007-08-02 16:07 ` Michael Buesch
2007-08-02 16:30   ` Larry Finger
2007-08-02 21:04     ` David Woodhouse
2007-08-02 21:06       ` Michael Buesch
2007-08-02 21:31       ` Larry Finger
2007-08-02 22:30       ` mac80211 IPv6 problems Daniel Drake
2007-08-02 22:36         ` Michael Buesch
2007-08-02 22:38           ` David Miller
2007-08-02 22:46         ` David Woodhouse
2007-08-03  0:55           ` John W. Linville
2007-08-03  8:02             ` Michael Wu
2007-08-06 17:05               ` John W. Linville [this message]
2007-08-08  3:19                 ` Michael Wu
2007-08-11  6:29                 ` Paul TBBle Hampson
2007-08-17  0:52                 ` Johannes Berg
2007-08-17 13:49                   ` John W. Linville
2007-08-19  2:45                     ` Paul TBBle Hampson
2007-08-03 10:40             ` David Woodhouse
2007-08-02 16:45   ` [RFC 0/10] Port of bcm43xx from softmac to mac80211 Erik Mouw
2007-08-02 17:25     ` Larry Finger

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=20070806170500.GE6442@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=dsd@gentoo.org \
    --cc=dwmw2@infradead.org \
    --cc=flamingice@sourmilk.net \
    --cc=jbenc@suse.cz \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.