From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Vasily Averin <vvs@parallels.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Cong Wang <amwang@redhat.com>
Subject: Re: [Bridge] bride: IPv6 multicast snooping enhancements
Date: Thu, 12 Feb 2015 12:41:17 +0100 [thread overview]
Message-ID: <20150212114117.GC3665@odroid> (raw)
In-Reply-To: <54DA0EAD.60002@parallels.com>
On Tue, Feb 10, 2015 at 04:59:09PM +0300, Vasily Averin wrote:
> I'm trying to fix ICMPv6 processing broken in OpenVZ after rebase to last RHEL6u6 kernel.
> After some unclear manipulation bridge begins to forward icmp6 NS (fe02::1) into wrong port,
> and at present I do not found the reason of this failure.
fe02::1 seems uncommon for ICMPv6 NS messages. Would you mind
making some dumps for ~10 minutes with tcpdump on all bridge ports
and the bridge interface itself with a filter "icmp6" and uploading the
result somewhere?
Also provide a dump from "bridge mdb show dev $bridge" please (if
possible - not sure whether that's available on the ancient 2.6.32
kernel as used on RHEL6u6).
Cheers, Linus
WARNING: multiple messages have this Message-ID (diff)
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Vasily Averin <vvs@parallels.com>
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Cong Wang <amwang@redhat.com>
Subject: Re: bride: IPv6 multicast snooping enhancements
Date: Thu, 12 Feb 2015 12:41:17 +0100 [thread overview]
Message-ID: <20150212114117.GC3665@odroid> (raw)
In-Reply-To: <54DA0EAD.60002@parallels.com>
On Tue, Feb 10, 2015 at 04:59:09PM +0300, Vasily Averin wrote:
> I'm trying to fix ICMPv6 processing broken in OpenVZ after rebase to last RHEL6u6 kernel.
> After some unclear manipulation bridge begins to forward icmp6 NS (fe02::1) into wrong port,
> and at present I do not found the reason of this failure.
fe02::1 seems uncommon for ICMPv6 NS messages. Would you mind
making some dumps for ~10 minutes with tcpdump on all bridge ports
and the bridge interface itself with a filter "icmp6" and uploading the
result somewhere?
Also provide a dump from "bridge mdb show dev $bridge" please (if
possible - not sure whether that's available on the ancient 2.6.32
kernel as used on RHEL6u6).
Cheers, Linus
next prev parent reply other threads:[~2015-02-12 11:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 0:13 [Bridge] bride: IPv6 multicast snooping enhancements Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-04 0:13 ` [Bridge] [PATCH net-next 1/2] bridge: prevent flooding IPv6 packets that do not have a listener Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-04 0:13 ` [Bridge] [PATCH net-next 2/2] bridge: apply multicast snooping to IPv6 link-local, too Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-04 0:13 ` Linus Lüssing
2013-09-05 16:36 ` [Bridge] bride: IPv6 multicast snooping enhancements David Miller
2013-09-05 16:36 ` David Miller
2013-09-05 16:36 ` David Miller
2015-02-10 8:44 ` [Bridge] " Vasily Averin
2015-02-10 8:44 ` Vasily Averin
2015-02-10 8:44 ` Vasily Averin
2015-02-10 11:44 ` [Bridge] " Linus Lüssing
2015-02-10 11:44 ` Linus Lüssing
2015-02-10 11:44 ` Linus Lüssing
2015-02-10 13:59 ` [Bridge] " Vasily Averin
2015-02-10 13:59 ` Vasily Averin
2015-02-10 13:59 ` Vasily Averin
2015-02-12 11:41 ` Linus Lüssing [this message]
2015-02-12 11:41 ` Linus Lüssing
2015-02-12 12:01 ` [Bridge] " Vasily Averin
2015-02-12 12:01 ` Vasily Averin
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=20150212114117.GC3665@odroid \
--to=linus.luessing@c0d3.blue \
--cc=amwang@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vvs@parallels.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 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.