All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: Jan Stancek <jstancek@redhat.com>
Cc: netdev@vger.kernel.org, Florian Westphal <fwestpha@redhat.com>,
	bridge@lists.linux-foundation.org
Subject: Re: [Bridge] bridge is not forwaring ICMP6 neighbor solicitation to KVM guest
Date: Tue, 4 Mar 2014 11:52:54 +0100	[thread overview]
Message-ID: <20140304105253.GC5090@Linus-Debian> (raw)
In-Reply-To: <624414844.12834668.1393920156458.JavaMail.zimbra@redhat.com>

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

Hi Jan,

On Tue, Mar 04, 2014 at 03:02:36AM -0500, Jan Stancek wrote:
> > For the broken query, ok, it's your manually crafted query. But
> > did you see a query with such a bogus source address "in the
> > wild", too? (I'm curious how urgent this sanity check is)
> 
> It's real packet I managed to capture during one such occurrence.
> I'm sending it with small C program over raw socket, but it's byte
> by byte exact copy of what I captured with tcpdump previously.
> 
> I'm not sure how that packet came to existence. Based on IPv6 address
> it came from host B, but all host B was doing at the time
> was running RHEL6 with couple qemu-kvm instances. KVM guests were
> set up to use bridge, so I'm assuming if any of them crafted
> this packet, source IPv6 address would be different.
> 

Ah, okay. Can you check whether it maybe came from the querier
code in the Linux bridge on host B? Is
"cat /sys/class/net/br0/bridge/multicast_querier" 1? Can you
isolate host B and disable any multicast router daemon on it? Then
check again, if you still see these queries. What kernel version
is running on host B?

Cheers, Linus

[-- 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: Jan Stancek <jstancek@redhat.com>
Cc: netdev@vger.kernel.org, Florian Westphal <fwestpha@redhat.com>,
	bridge@lists.linux-foundation.org
Subject: Re: bridge is not forwaring ICMP6 neighbor solicitation to KVM guest
Date: Tue, 4 Mar 2014 11:52:54 +0100	[thread overview]
Message-ID: <20140304105253.GC5090@Linus-Debian> (raw)
In-Reply-To: <624414844.12834668.1393920156458.JavaMail.zimbra@redhat.com>

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

Hi Jan,

On Tue, Mar 04, 2014 at 03:02:36AM -0500, Jan Stancek wrote:
> > For the broken query, ok, it's your manually crafted query. But
> > did you see a query with such a bogus source address "in the
> > wild", too? (I'm curious how urgent this sanity check is)
> 
> It's real packet I managed to capture during one such occurrence.
> I'm sending it with small C program over raw socket, but it's byte
> by byte exact copy of what I captured with tcpdump previously.
> 
> I'm not sure how that packet came to existence. Based on IPv6 address
> it came from host B, but all host B was doing at the time
> was running RHEL6 with couple qemu-kvm instances. KVM guests were
> set up to use bridge, so I'm assuming if any of them crafted
> this packet, source IPv6 address would be different.
> 

Ah, okay. Can you check whether it maybe came from the querier
code in the Linux bridge on host B? Is
"cat /sys/class/net/br0/bridge/multicast_querier" 1? Can you
isolate host B and disable any multicast router daemon on it? Then
check again, if you still see these queries. What kernel version
is running on host B?

Cheers, Linus

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

  reply	other threads:[~2014-03-04 10:52 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       ` [Bridge] " Linus Lüssing
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           ` Linus Lüssing [this message]
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=20140304105253.GC5090@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 \
    /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.