All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: netdev@vger.kernel.org, Florian Westphal <fwestpha@redhat.com>,
	bridge@lists.linux-foundation.org,
	Jan Stancek <jstancek@redhat.com>
Subject: Re: [Bridge] bridge is not forwaring ICMP6 neighbor solicitation to KVM guest
Date: Tue, 4 Mar 2014 00:03:23 +0100	[thread overview]
Message-ID: <20140303230323.GX5090@Linus-Debian> (raw)
In-Reply-To: <5314F6D8.2050701@gmail.com>

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

On Mon, Mar 03, 2014 at 04:40:40PM -0500, Vlad Yasevich wrote:
> I did notice a minor issue in the bridge code.  The following
> code:
>        /* Prevent flooding this packet if there is no listener present */
>         if (!ipv6_addr_is_ll_all_nodes(&ip6h->daddr))
>                 BR_INPUT_SKB_CB(skb)->mrouters_only = 1;
> 
>         if (ip6h->nexthdr != IPPROTO_HOPOPTS ||
>             ip6h->payload_len == 0)
>                 return 0;
> 
> will mark most multicast traffic is mrouters_only.  The two
> statement should be probably be reversed.  However, that's shouldn't
> cause the reported problem.

Reversing the order of these two if-clauses would reintroduce the issue
this commit tried to address, I think:
"bridge: prevent flooding IPv6 packets that do not have a listener"

Besides, I don't quite see what minor issue you are refering to,
would you mind being a little more verbose?

Cheers, Linus

PS: mrouters_only has a kind of confusing naming... for
MLD/IGMP packets it means sending to multicast routers only, there
the name fits. But for non-MLD/IGMP packets it means something
else since "bridge: Only flood unregistered groups to routers"
(and I went along with it with "bridge: prevent flooding IPv6 packets
that do not have a listener"), there it means dropping the skb if
there is no router or matching listener.

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

WARNING: multiple messages have this Message-ID (diff)
From: "Linus Lüssing" <linus.luessing@web.de>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: netdev@vger.kernel.org, Florian Westphal <fwestpha@redhat.com>,
	bridge@lists.linux-foundation.org,
	Jan Stancek <jstancek@redhat.com>
Subject: Re: bridge is not forwaring ICMP6 neighbor solicitation to KVM guest
Date: Tue, 4 Mar 2014 00:03:23 +0100	[thread overview]
Message-ID: <20140303230323.GX5090@Linus-Debian> (raw)
In-Reply-To: <5314F6D8.2050701@gmail.com>

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

On Mon, Mar 03, 2014 at 04:40:40PM -0500, Vlad Yasevich wrote:
> I did notice a minor issue in the bridge code.  The following
> code:
>        /* Prevent flooding this packet if there is no listener present */
>         if (!ipv6_addr_is_ll_all_nodes(&ip6h->daddr))
>                 BR_INPUT_SKB_CB(skb)->mrouters_only = 1;
> 
>         if (ip6h->nexthdr != IPPROTO_HOPOPTS ||
>             ip6h->payload_len == 0)
>                 return 0;
> 
> will mark most multicast traffic is mrouters_only.  The two
> statement should be probably be reversed.  However, that's shouldn't
> cause the reported problem.

Reversing the order of these two if-clauses would reintroduce the issue
this commit tried to address, I think:
"bridge: prevent flooding IPv6 packets that do not have a listener"

Besides, I don't quite see what minor issue you are refering to,
would you mind being a little more verbose?

Cheers, Linus

PS: mrouters_only has a kind of confusing naming... for
MLD/IGMP packets it means sending to multicast routers only, there
the name fits. But for non-MLD/IGMP packets it means something
else since "bridge: Only flood unregistered groups to routers"
(and I went along with it with "bridge: prevent flooding IPv6 packets
that do not have a listener"), there it means dropping the skb if
there is no router or matching listener.

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

  reply	other threads:[~2014-03-03 23:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1566805413.12693479.1393872931017.JavaMail.zimbra@redhat.com>
2014-03-03 19:47 ` bridge is not forwaring ICMP6 neighbor solicitation to KVM guest Jan Stancek
2014-03-03 21:27   ` [Bridge] " Linus Lüssing
2014-03-03 21:27     ` Linus Lüssing
2014-03-03 21:40     ` [Bridge] " Vlad Yasevich
2014-03-03 21:40       ` Vlad Yasevich
2014-03-03 23:03       ` Linus Lüssing [this message]
2014-03-03 23:03         ` Linus Lüssing
2014-03-03 22:45     ` [Bridge] " Jan Stancek
2014-03-03 22:45       ` Jan Stancek
2014-03-04  0:00       ` [Bridge] " Linus Lüssing
2014-03-04  0:00         ` Linus Lüssing
2014-03-04  8:02         ` [Bridge] " Jan Stancek
2014-03-04  8:02           ` Jan Stancek
2014-03-04 10:52           ` [Bridge] " Linus Lüssing
2014-03-04 10:52             ` Linus Lüssing
2014-03-04 11:06             ` [Bridge] " Jan Stancek
2014-03-04 11:06               ` Jan Stancek
2014-03-04 21:37               ` [Bridge] " Linus Lüssing
2014-03-04 21:37                 ` Linus Lüssing
2014-03-05 12:10                 ` [Bridge] " Jan Stancek
2014-03-05 12:10                   ` Jan Stancek
2014-03-05 14:27                   ` [Bridge] " Linus Lüssing
2014-03-05 14:27                     ` Linus Lüssing
2014-03-05 14:57                     ` [Bridge] " Jan Stancek
2014-03-05 14:57                       ` Jan Stancek
2014-03-12  4:37                       ` [Bridge] " Linus Lüssing
2014-03-12  4:37                         ` Linus Lüssing
2014-03-12  7:45                         ` [Bridge] " Jan Stancek
2014-03-12  7:45                           ` Jan Stancek

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=20140303230323.GX5090@Linus-Debian \
    --to=linus.luessing@web.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=fwestpha@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevich@gmail.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.