From: David Miller <davem@davemloft.net>
To: jbenc@redhat.com
Cc: brandon.philips@coreos.com, netdev@vger.kernel.org,
tom@tigera.io, aaron.levy@coreos.com, bison@coreos.com
Subject: Re: fib_frontend: Add network specific broadcasts, when it takes a sense
Date: Mon, 12 Dec 2016 10:03:39 -0500 (EST) [thread overview]
Message-ID: <20161212.100339.37679235285289515.davem@davemloft.net> (raw)
In-Reply-To: <20161212153035.4a751ccc@griffin>
From: Jiri Benc <jbenc@redhat.com>
Date: Mon, 12 Dec 2016 15:30:35 +0100
> On Fri, 9 Dec 2016 15:41:52 -0800, Brandon Philips wrote:
>> 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.
>
> Are you saying you're trying to assign the IP address 10.4.0.0/16 as a
> unicast address to an interface? Then you'll run into way more problems
> than the one you're describing. You can't have host part of the IP
> address consisting of all zeros (or all ones). Just don't do it. Choose
> a valid IP address instead.
Agreed.
next prev parent reply other threads:[~2016-12-12 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-10 0:07 Brandon Philips
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=20161212.100339.37679235285289515.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aaron.levy@coreos.com \
--cc=bison@coreos.com \
--cc=brandon.philips@coreos.com \
--cc=jbenc@redhat.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 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).