Linux wireless drivers development
 help / color / mirror / Atom feed
From: Paul TBBle Hampson <Paul.Hampson@Pobox.com>
To: linux-wireless@vger.kernel.org
Subject: Re: mac80211 IPv6 problems
Date: Sat, 11 Aug 2007 16:29:21 +1000	[thread overview]
Message-ID: <20070811062921.GA27009@keitarou> (raw)
In-Reply-To: <20070806170500.GE6442@tuxdriver.com>

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

On Mon, Aug 06, 2007 at 01:05:00PM -0400, John W. Linville wrote:
> 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>

Worked for me, on bcm43xx-mac80211. Got an IP address from radvd, and
was able to ping6 a couple of places out on the big bad Internet.

Whole kernel is built from wireless-dev,
f2b262a6a8771fe9595f2c08e9d598b97634b266.

Thanks. ^_^

-- 
-----------------------------------------------------------
Paul "TBBle" Hampson, B.Sc, LPI, MCSE
Very-later-year Asian Studies student, ANU
The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361)
Paul.Hampson@Pobox.com

Of course Pacman didn't influence us as kids. If it did,
we'd be running around in darkened rooms, popping pills and
listening to repetitive music.
 -- Kristian Wilson, Nintendo, Inc, 1989

License: http://creativecommons.org/licenses/by/2.1/au/
-----------------------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-08-11  6:29 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
2007-08-08  3:19                 ` Michael Wu
2007-08-11  6:29                 ` Paul TBBle Hampson [this message]
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=20070811062921.GA27009@keitarou \
    --to=paul.hampson@pobox.com \
    --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