From: Brandon Philips <brandon.philips@coreos.com>
To: netdev@vger.kernel.org, Tom Denham <tom@tigera.io>,
Aaron Levy <aaron.levy@coreos.com>, Brad Ison <bison@coreos.com>
Subject: fib_frontend: Add network specific broadcasts, when it takes a sense
Date: Fri, 9 Dec 2016 16:07:52 -0800 [thread overview]
Message-ID: <20161210000752.GA18080@Brandons-MacBook-Pro.local> (raw)
Hello-
A number of us are working on an OSS overlay network system called flannel.
It is used in a variety of Linux container systems and one of the backends
is VXLAN.
The issue we have: when creating the VXLAN interface and assigning it an
address we see a broadcast route being added by the Kernel. For example if
we have 10.4.0.0/16 a broadcast route to 10.4.0.0 is created. This route is
unwanted because we assign 10.4.0.0 to one of our VXLAN interfaces.
However, the Kernel interface bring-up comment reads: Add network specific
broadcasts, when it takes a sense. The code is here:
https://github.com/torvalds/linux/blob/master/net/ipv4/fib_frontend.c#L859-L872
Can someone explain why creation of the broadcast route is non-optional?
Would a patch to make it optional be acceptable? Is it safe for us to
simply delete the route? We have a patch that simply deletes the broadcast
route after interface creation but don't know why the Kernel code "makes
sense".
You can read more information about the issue here:
https://github.com/coreos/flannel/pull/569
Thank You,
Brandon
next reply other threads:[~2016-12-10 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 0:07 Brandon Philips [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-09 23:41 fib_frontend: Add network specific broadcasts, when it takes a sense Brandon Philips
2016-12-12 14:30 ` Jiri Benc
2016-12-12 14:44 ` Brandon Philips
2016-12-12 14:52 ` Jiri Benc
2016-12-12 16:52 ` Hannes Frederic Sowa
2016-12-12 15:03 ` David Miller
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=20161210000752.GA18080@Brandons-MacBook-Pro.local \
--to=brandon.philips@coreos.com \
--cc=aaron.levy@coreos.com \
--cc=bison@coreos.com \
--cc=netdev@vger.kernel.org \
--cc=tom@tigera.io \
/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.