From: "Marc St-Onge" <marc.st-onge@canadiansignals.com>
To: <netdev@vger.kernel.org>
Subject: Multicast GRE changed behaviour
Date: Mon, 16 Feb 2015 20:17:53 -0500 [thread overview]
Message-ID: <003301d04a4f$8e1691e0$aa43b5a0$@canadiansignals.com> (raw)
In-Reply-To:
I'm not 100% sure if the issue we are facing is related to recent changes in
ip_gre.c but while I was reading through the code I came about the comment
on line 341 and suspect some changes may have been introduced in ip_gre.c.
We have been using Multicast GRE tunnels in our organisation (we actually
call it Broadcast GRE and have given it the BGRE acronym) but essentially,
we successfully setup the tunnels exactly as described in the example.
The recent Ubuntu upgrade has caused an backward compatibility issue
somewhere between kernel 3.8 and 3.13. The previous kernel would use
Multicast to do the ARP and discovery as well as encapsulation of Multicast
user traffic and would use the end-point Unicast address to encapsulate the
Unicast user traffic between the remote nodes. In Kernel 3.13 we are
observing that the Unicast traffic is also encapsulated in a Multicast
datagram.
Marc St-Onge
reply other threads:[~2015-02-17 1:24 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='003301d04a4f$8e1691e0$aa43b5a0$@canadiansignals.com' \
--to=marc.st-onge@canadiansignals.com \
--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