From: Dennis Jacobfeuerborn <dennisml@conversis.de>
To: netfilter@vger.kernel.org
Subject: Re: multicast traffic no longer working after reboot
Date: Thu, 31 Jul 2014 17:24:07 +0200 [thread overview]
Message-ID: <53DA5F97.7010905@conversis.de> (raw)
In-Reply-To: <53DA432C.7050907@conversis.de>
On 31.07.2014 15:22, Dennis Jacobfeuerborn wrote:
> Hi,
> today a couple of Hypervisors got restarted due to a power outage. While
> the systems and the VMs on the are running fine multicast traffic
> between the guests is no longer working.
>
> I generate multicast udp packet using iperf in the guest and check on
> the host using tcpdump:
>
> tcpdump vnet0 => multicast packets are visible
> tcpdump vlanbr8 => multicast packets are visible
> tcpdump em1.8 => no multicast packets visible
>
> vlanbr8 is the bridge, vnet0 the interface of the guest and em1.8 the
> physical interface for vlan 8.
>
> I compared the settings in /sys/class/net/vlanbr8/bridge/multicast_*
> with a system where multicast works fine and see no differences. brctl
> showstp also shows "mc router" to be 1 for both interfaces and the
> bridge. All settings in /proc/sys/net/bridge/* are 0.
>
> Any ideas why the bridge doesn't seem to forward multicast packets?
> iperf with unicast udp also works fine so it's just multicast that is
> the problem.
>
> Regards,
> Dennis
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I did some further testing and strangely enough after booting the HV and
the guest things work as expected but after 2-3 minutes I suddenly don't
see the the packets anymore on em1.8. This is really bizarre behavior.
Regards,
Dennis
prev parent reply other threads:[~2014-07-31 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 13:22 multicast traffic no longer working after reboot Dennis Jacobfeuerborn
2014-07-31 15:24 ` Dennis Jacobfeuerborn [this message]
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=53DA5F97.7010905@conversis.de \
--to=dennisml@conversis.de \
--cc=netfilter@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.