netdev - Fw: [Bug 97961] New: macvtap does not transport IPv4 multicast packets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 8 May 2015 12:51:42 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	netdev@...r.kernel.org
Subject: Fw: [Bug 97961] New: macvtap does not transport IPv4 multicast
 packets



Begin forwarded message:

Date: Fri, 8 May 2015 19:50:20 +0000
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "shemminger@...ux-foundation.org" <shemminger@...ux-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@...ux-foundation.org
          Reporter: mh+kernel-bugzilla@...schlus.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html