From: Bernhard Schmidt <berni@birkenwald.de>
To: netdev@vger.kernel.org
Subject: Re: VXLAN multicast receive not working
Date: Sat, 24 Nov 2012 01:24:42 +0000 (UTC) [thread overview]
Message-ID: <k8p7kq$p65$1@ger.gmane.org> (raw)
In-Reply-To: k8p35s$pd6$1@ger.gmane.org
Bernhard Schmidt <berni@birkenwald.de> wrote:
>>> The same VXLAN domain is defined on the Nexus 1000V and a VM is attached
>>> to it. When I send some broadcast traffic down vxlan0 (i.e. ping
>>> 10.1.1.2 which generates an ARP request) the VM sees the packet just
>>> fine.
>>>
>>> When I do it the other way around (the VM sends a broadcast ARP for
>>> 10.1.1.3) I see a packet coming into eth1 on the multicast group, but
>>> vxlan0 stays silent.
>>
>> I think I found a possible reason, my vxlan interface is on top of eth1
>>
>> 7: vxlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue
>> state UNKNOWN mode DEFAULT
>> link/ether 96:06:c6:cf:a0:2e brd ff:ff:ff:ff:ff:ff
>> vxlan id 12340 group 239.0.0.42 dev eth1 port 32768 61000 ageing 300
>>
>> but the multicast group is joined only on eth0
>
> Confirmed working as soon as eth0 can receive the group multicast
> address (connected to the same VLAN), even if the vxlan0 interface is
> still configured to eth1.
When swapping the configuration around using eth0 for the VXLAN
transport and eth1 for Management, the group is joined on eth1. It is
always joined where the default route points, so it looks like the
interface is not set at all.
# ip route add <group>/32 dev <vxlanintf>
works around the problem.
Bernhard
next prev parent reply other threads:[~2012-11-24 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 0:05 VXLAN multicast receive not working Bernhard Schmidt
2012-11-22 0:09 ` Bernhard Schmidt
2012-11-24 0:08 ` Bernhard Schmidt
2012-11-24 1:24 ` Bernhard Schmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-21 23:27 Bernhard Schmidt
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='k8p7kq$p65$1@ger.gmane.org' \
--to=berni@birkenwald.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 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.