public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 97961] New: macvtap does not transport IPv4 multicast packets
Date: Fri, 8 May 2015 12:51:42 -0700	[thread overview]
Message-ID: <20150508125142.5dadf9e7@urahara> (raw)



Begin forwarded message:

Date: Fri, 8 May 2015 19:50:20 +0000
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "shemminger@linux-foundation.org" <shemminger@linux-foundation.org>
Subject: [Bug 97961] New: macvtap does not transport IPv4 multicast packets


https://bugzilla.kernel.org/show_bug.cgi?id=97961

            Bug ID: 97961
           Summary: macvtap does not transport IPv4 multicast packets
           Product: Networking
           Version: 2.5
    Kernel Version: 4.0.2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IPV4
          Assignee: shemminger@linux-foundation.org
          Reporter: mh+kernel-bugzilla@zugschlus.de
        Regression: No

Hi,

I have a system running Debian Jessie and kernel 4.0.2 (self-built). When I
start a VM (also Debian Jessie) in kvm which has its network connected via
macvtap, IPv4 multicast packets do not show up on the macvtap interface and
also not inside the VM. This can easily be observed when avahi is in use.

tcpdump on enp3s0:
21:44:24.855171 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)
21:44:24.855242 IP 192.168.251.21.5353 > 224.0.0.251.5353: 0 A (QM)?
parada.local. (30)
21:44:25.856546 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)
21:44:25.856617 IP 192.168.251.21.5353 > 224.0.0.251.5353: 0 A (QM)?
parada.local. (30)
21:44:27.858923 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)
21:44:27.858995 IP 192.168.251.21.5353 > 224.0.0.251.5353: 0 A (QM)?
parada.local. (30)

tcpdump on macvtap0:
21:44:40.113076 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)
21:44:41.114809 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)
21:44:43.117490 IP6 2a01:238:4071:321e:224:d7ff:fed0:5adc.5353 > ff02::fb.5353:
0 A (QM)? parada.local. (30)

The avahid on the VM does not answer the IPv6 packets since it is configured
not to answer A queries over IPv6.

Using a regular bridge to connect the VM via the shared device model works.

I do not know whether this is a regression since I never tried with older
kernels, I have never tried macvtap before.

Greetings
Marc

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2015-05-08 19:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150508125142.5dadf9e7@urahara \
    --to=stephen@networkplumber.org \
    --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