From: Eric Dumazet <eric.dumazet@gmail.com>
To: Chris Boot <bootc@bootc.net>
Cc: David Miller <davem@davemloft.net>,
lkml <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference in ipv6_select_ident
Date: Thu, 22 Dec 2011 18:41:32 +0100 [thread overview]
Message-ID: <1324575692.2586.6.camel@edumazet-laptop> (raw)
In-Reply-To: <4EF352A2.2090604@bootc.net>
Le jeudi 22 décembre 2011 à 15:54 +0000, Chris Boot a écrit :
> Eric,
>
> I'm seeing a new problem now with IPv6 on my bridge, I don't know if
> it's related to any of the patches you gave me.
>
> Basically, I have eth0 and eth1 in a balance-rr bond (bond0), and this
> is added as a port in a bridge. When the bond and bridge are freshly
> brought up, IPv4 works fine but it appears to be deaf to IPv6 traffic.
> It stays this way until I run 'tcpdump -i eth0' and 'tcpdump -i eth1'.
> If I run tcpdump with the -p flag to not enable promiscuous mode, the
> interfaces remain deaf. Only if they enter promiscuous mode do they
> start to listen to each other. It also doesn't help to run tcpdump
> against bond0 or br0 at all.
>
> I'm not sure if once I've killed tcpdump they become deaf again, but I
> have enough IPv6 traffic to keep the neighbour entry alive.
Thats probably a separate issue. It would be better to open a new thread
on netdev, instead of continuing this one.
IPv6 needs multicast capabilities, so maybe balance-rr bonding mode is
not propagating multicat filters properly on both nics.
It might be a problem on one of your NIC.
(tcpdump automatically installs promiscous mode, so all multicast frames
are received, regardless of previous multicast filters in place)
next prev parent reply other threads:[~2011-12-22 17:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 15:52 Chris Boot
2011-12-21 16:29 ` Eric Dumazet
2011-12-21 17:03 ` Chris Boot
2011-12-21 17:36 ` Eric Dumazet
2011-12-21 18:00 ` Eric Dumazet
2011-12-21 20:05 ` Chris Boot
2011-12-21 20:28 ` Eric Dumazet
2011-12-21 20:52 ` Eric Dumazet
2011-12-21 21:58 ` Chris Boot
2011-12-21 23:12 ` Chris Boot
2011-12-22 4:37 ` Eric Dumazet
2011-12-22 6:00 ` [PATCH] bridge: provide a mtu() method for fake_dst_ops Eric Dumazet
2011-12-22 7:05 ` Steffen Klassert
2011-12-22 6:38 ` BUG: unable to handle kernel NULL pointer dereference in ipv6_select_ident Steffen Klassert
2011-12-22 7:51 ` Eric Dumazet
2011-12-22 7:58 ` Steffen Klassert
2011-12-22 8:05 ` Eric Dumazet
2011-12-22 10:01 ` Steffen Klassert
2011-12-22 10:04 ` Chris Boot
2011-12-22 14:15 ` Eric Dumazet
2011-12-22 15:54 ` Chris Boot
2011-12-22 17:41 ` Eric Dumazet [this message]
2011-12-22 18:29 ` David Miller
2011-12-23 3:38 ` David Miller
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=1324575692.2586.6.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=bootc@bootc.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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
all inboxes | Powered by JetHome®