Netdev List
 help / color / mirror / Atom feed
From: Pekka Savola <pekkas@netcore.fi>
To: netdev@vger.kernel.org
Subject: Re: zd1211rw and mac80211: multicast/v6 doesn't work in 2.6.21.5
Date: Tue, 31 Jul 2007 11:27:22 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707311124560.8287@netcore.fi> (raw)
In-Reply-To: <Pine.LNX.4.64.0706280814090.21541@netcore.fi>

FWIW,

multicast/v6 is still broken on zd1211rw on 2.6.22.1 based Fedora 7 
kernel (2.6.22.1-33.fc7).

On Thu, 28 Jun 2007, Pekka Savola wrote:
> On Fedora 7 (kernel 2.6.21-1.3228.fc7, based on 2.6.21.5), my 
> zd1211rw_mac80211 WLAN USB stick and multicast/v6 no longer works. On Fedora 
> 6 (kernel 2.6.20, no mac80211) it was OK.
>
> I get "wlan0: duplicate address detected!" on dmesg when the kernel is trying 
> to autoconfigure a global address.
>
> I suppose this is caused by the IPv6 stack seeing my own ICMPv6 neighbor 
> solicitation and thinking it was originated by someone else:
>
> 08:46:21.762807 00:02:72:5b:dc:28 > 33:33:ff:5b:dc:28, ethertype IPv6 
> (0x86dd), length 78: (hlim 255, next-header: ICMPv6 (58), length: 24) :: > 
> ff02::1:ff5b:dc28: [icmp6 sum ok] ICMP6, neighbor solicitation, length 24, 
> who has 2001:708:10:90:202:72ff:fe5b:dc28
>
> Strangely, the same error isn't printed with the link-local address which 
> uses the same EUI-64.
>
> z1211rw Wiki seems to imply that this might be an issue in generic mac80211 
> code:
>
> http://www.linuxwireless.org/en/users/Drivers/zd1211rw/mac80211Issues
>
> It'd be nice to get this fixed.  Or has it already been?
>
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

      reply	other threads:[~2007-07-31  8:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28  5:51 zd1211rw and mac80211: multicast/v6 doesn't work in 2.6.21.5 Pekka Savola
2007-07-31  8:27 ` Pekka Savola [this message]

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=Pine.LNX.4.64.0707311124560.8287@netcore.fi \
    --to=pekkas@netcore.fi \
    --cc=netdev@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