From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: fib_frontend: Add network specific broadcasts, when it takes a sense Date: Mon, 12 Dec 2016 10:03:39 -0500 (EST) Message-ID: <20161212.100339.37679235285289515.davem@davemloft.net> References: <20161212153035.4a751ccc@griffin> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: brandon.philips@coreos.com, netdev@vger.kernel.org, tom@tigera.io, aaron.levy@coreos.com, bison@coreos.com To: jbenc@redhat.com Return-path: Received: from shards.monkeyblade.net ([184.105.139.130]:58730 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752728AbcLLPDo (ORCPT ); Mon, 12 Dec 2016 10:03:44 -0500 In-Reply-To: <20161212153035.4a751ccc@griffin> Sender: netdev-owner@vger.kernel.org List-ID: From: Jiri Benc 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.