Break out the discussion of special and reserved IPv4 addresses into a subsection, and briefly describe three cases in which Linux no longer treats addresses specially, where other systems do or did. The divergences in Linux's behavior mentioned in this patch were introduced at unicast 240/4 (since 2.6.25): commit 1e637c74b0f84eaca02b914c0b8c6f67276e9697 Author: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> Date: Mon Jan 21 03:18:08 2008 -0800 unicast 0/8 (since 5.3): commit 96125bf9985a75db00496dd2bc9249b777d2b19b Author: Dave Taht <dave.taht@xxxxxxxxx> Date: Sat Jun 22 10:07:34 2019 -0700 unicast subnet lowest address (since 5.14): commit 58fee5fc83658aaacf60246aeab738946a9ba516 Merge: 77091933e453 6101ca0384e3 Author: David S. Miller <davem@xxxxxxxxxxxxx> Date: Mon May 17 13:47:58 2021 -0700 Signed-off-by: Seth David Schoen <schoen@xxxxxxxxxxx> Suggested-by: John Gilmore <gnu@xxxxxxxx> --- man7/ip.7 | 38 +++++++++++++++++++++++++++++++++++--- 1 file changed, 35 insertions(+), 3 deletions(-) diff --git a/man7/ip.7 b/man7/ip.7 index f69af1b32..94de21979 100644 --- a/man7/ip.7 +++ b/man7/ip.7 @@ -237,6 +237,7 @@ In particular, this means that you need to call on the number that is assigned to a port. All address/port manipulation functions in the standard library work in network byte order. +.SS Special and reserved addresses .PP There are several special addresses: .B INADDR_LOOPBACK @@ -244,12 +245,43 @@ There are several special addresses: always refers to the local host via the loopback device; .B INADDR_ANY (0.0.0.0) -means any address for binding; +means any address for socket binding; .B INADDR_BROADCAST (255.255.255.255) -means any host and has the same effect on bind as +has the same effect on socket binding as .B INADDR_ANY -for historical reasons. +for historical reasons. A packet addressed to +.B INADDR_BROADCAST +through a socket which has +.B SO_BROADCAST +set will be broadcast to all hosts on the local network segment, as +long as the link is broadcast-capable. +.PP +On any locally-attached IP subnet with a link type that supports +broadcasts, the highest-numbered address (e.g., the .255 address on a +subnet with netmask 255.255.255.0) is designated as a broadcast address. +This "broadcast address" cannot usefully be assigned to an interface, and +can only be addressed with a socket on which the +.B SO_BROADCAST +option has been set. +Internet standards have historically also reserved the lowest-numbered +address (e.g., the .0 address on a subnet with netmask 255.255.255.0) +for broadcast, though they call it "obsolete" for this purpose. Since +Linux 5.14, it is treated as an ordinary unicast address. +.PP +Internet standards have also traditionally reserved various addresses +for particular uses, though Linux no longer treats some of these +specially. Addresses in the ranges 0.0.0.1 through 0.255.255.255 and +240.0.0.0 through 255.255.255.254 (0/8 and 240/4) are reserved globally. +Since Linux 5.3 and Linux 2.6.245, respectively, the 0/8 and 240/4 +addresses are treated as ordinary unicast addresses. Systems that follow +the traditional behaviors may not interoperate with these historically +reserved addresses. +.PP +All addresses from 127.0.0.1 through 127.255.255.254 +are treated as loopback addresses akin to the standardized +local loopback address 127.0.0.1, while addresses in 224.0.0.0 through +239.255.255.255 (224/4) are dedicated to multicast use. .SS Socket options IP supports some protocol-specific socket options that can be set with .BR setsockopt (2) -- 2.25.1
