public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Seth David Schoen <schoen@loyalty.org>
Cc: linux-man@vger.kernel.org, gnu@toad.com
Subject: Re: [PATCH 1/1] ip.7: Add "special and reserved addresses" section
Date: Sat, 20 Mar 2021 20:49:59 +0100	[thread overview]
Message-ID: <87ft0pzjtk.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20210320002041.GZ2289@frotz.zork.net> (Seth David Schoen's message of "Fri, 19 Mar 2021 17:20:41 -0700")

* Seth David Schoen:

> +On any locally-attached IP subnet, the lowest-numbered address and
> +highest-numbered address (e.g., the .0 and .255 addresses on a subnet
> +with netmask 255.255.255.0) are both designated as broadcast addresses.
> +These cannot usefully be assigned to an interface, and can only be
> +addressed with a socket on which the
> +.B SO_BROADCAST
> +option has been explicitly enabled.

I think the broadcast address is actually settable to some degree, and
/31 subnets do not have them.  I wouldn't be surprised if kernel
behavior also depended on the network device.

  reply	other threads:[~2021-03-20 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  0:20 [PATCH 1/1] ip.7: Add "special and reserved addresses" section Seth David Schoen
2021-03-20 19:49 ` Florian Weimer [this message]
2021-03-22 17:58   ` Seth David Schoen
2021-03-22 21:29     ` Seth David Schoen
2021-03-24  7:07       ` John Gilmore
2021-03-24  8:26     ` Florian Weimer
2021-03-24 19:18       ` Seth David Schoen
2021-03-26 22:53         ` Seth David Schoen
2021-03-26 23:45           ` John Gilmore
2021-03-27  0:22             ` Seth David Schoen
2021-03-30  3:21           ` [PATCH v2] " Seth David Schoen
2021-05-06  2:37             ` [RESEND PATCH " Seth David Schoen

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=87ft0pzjtk.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gnu@toad.com \
    --cc=linux-man@vger.kernel.org \
    --cc=schoen@loyalty.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