From: Stefan Bauer <sb@plzk.de>
To: netdev@vger.kernel.org
Subject: Re: ip link macvtap interface not processing specific ipv6 multicast traffic without promiscuous mode on
Date: Wed, 15 Apr 2015 10:21:55 +0200 [thread overview]
Message-ID: <1429086115.3383.36.camel@plzk.de> (raw)
In-Reply-To: <1428598288.2759.2.camel@plzk.de>
I could narrow down the problem. Win7Prof and Windows 10 is having this
issue.
Win Client is member of the multicast group and is listening on
ff02::1:ffdf:fe88
Traffic from router -> client - captured on router:
07:41:23.104567 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
07:41:24.099764 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
07:41:25.099772 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
Traffic from router to client - captured on KVM HOST
09:41:23.106444 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
09:41:24.101647 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
09:41:25.101718 IP6 fe80::12fe:edff:fee6:cfa > ff02::1:ffdf:fe88: ICMP6,
neighbor solicitation, who has 2a01:198:200:8350:851e:21a7:28df:fe88,
length 32
No traffic seen on KVM GUEST (win7 or win10) with wireshark
Any ideas to debug this further?
Cheers
Stefan
next prev parent reply other threads:[~2015-04-15 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 10:09 ip link macvtap interface not processing specific ipv6 multicast traffic without promiscuous mode on Stefan Bauer
2015-04-09 16:51 ` Stefan Bauer
2015-04-15 8:21 ` Stefan Bauer [this message]
2015-04-15 8:38 ` [SOLVED]Re: " Stefan Bauer
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=1429086115.3383.36.camel@plzk.de \
--to=sb@plzk.de \
--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;
as well as URLs for NNTP newsgroup(s).