From: Guillaume Nault <gnault@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: David Ahern <dsahern@gmail.com>, Xin Long <lucien.xin@gmail.com>,
network dev <netdev@vger.kernel.org>, davem <davem@davemloft.net>,
mmhatre@redhat.com,
"alexander.h.duyck@intel.com" <alexander.h.duyck@intel.com>
Subject: Re: route: an issue caused by local and main table's merge
Date: Tue, 10 Mar 2020 16:56:30 +0100 [thread overview]
Message-ID: <20200310155630.GA7102@pc-3.home> (raw)
In-Reply-To: <CAKgT0UcbycqgrfviqUmvS9S7+F6q-gMzrz-KKQuEb77ruZZLRQ@mail.gmail.com>
On Mon, Mar 09, 2020 at 08:53:53AM -0700, Alexander Duyck wrote:
> Also, is it really a valid configuration to have the same address
> configured as both a broadcast and unicast address? I couldn't find
> anything that said it wasn't, but at the same time I haven't found
> anything saying it is an acceptable practice to configure an IP
> address as both a broadcast and unicast destination. Everything I saw
> seemed to imply that a subnet should be at least a /30 to guarantee a
> pair of IPs and support for broadcast addresses with all 1's and 0 for
> the host identifier. As such 192.168.122.1 would never really be a
> valid broadcast address since it implies a /31 subnet mask.
>
RFC 3031 explicitly allows /31 subnets for point to point links. Also,
I've seen such network configurations in production on Linux boxes.
next prev parent reply other threads:[~2020-03-10 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 8:38 route: an issue caused by local and main table's merge Xin Long
2020-03-09 2:29 ` David Ahern
2020-03-09 15:53 ` Alexander Duyck
2020-03-10 15:56 ` Guillaume Nault [this message]
2020-03-10 16:01 ` Guillaume Nault
2020-03-10 17:19 ` Alexander Duyck
2020-03-11 16:28 ` Guillaume Nault
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=20200310155630.GA7102@pc-3.home \
--to=gnault@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=lucien.xin@gmail.com \
--cc=mmhatre@redhat.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 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.