From: Rick Jones <rick.jones2@hp.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ulrich Drepper <drepper@redhat.com>,
netdev <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: follow-up: discrepancy with POSIX
Date: Wed, 19 Sep 2007 11:38:57 -0700 [thread overview]
Message-ID: <46F16CC1.9090302@hp.com> (raw)
In-Reply-To: <20070919183004.GA18707@one.firstfloor.org>
Andi Kleen wrote:
> On Wed, Sep 19, 2007 at 11:02:00AM -0700, Ulrich Drepper wrote:
>
>>>on UDP/RAW and it's certainly possible to connect() to that.
>>
>>Where do you get this from? And where is this implemented? I don't
>
>
> Sorry it's actually loopback, not broadcast as implemented in Linux.
> In Linux it's implemented in ip_route_output_slow(). Essentially
> converted to 127.0.0.1
>
> I think it's traditional BSD behaviour but couldn't find it on
> a quick look in FreeBSD source (but haven't looked very intensively)
One has to set their way-back machine pretty far back to find the *BSD
bits which used 0.0.0.0 as the "all nets, all subnets" (to mis-use a
term) broadcast IPv4 address when sending. Perhaps as far back as the
time before HP-UX 7 or SunOS4. The bit errors in my dimm memory get
pretty dense that far back...
It has hung-on in various places (stacks) as an "accepted" broadcast IP
in the receive path, but not the send path for quite possibly decades now.
rick jones
next prev parent reply other threads:[~2007-09-19 18:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 15:21 follow-up: discrepancy with POSIX Ulrich Drepper
2007-09-19 15:47 ` Andi Kleen
2007-09-19 16:49 ` Ulrich Drepper
2007-09-19 16:52 ` David Miller
2007-09-19 17:04 ` Ulrich Drepper
2007-09-19 17:27 ` Ulrich Drepper
2007-09-19 17:26 ` Andi Kleen
2007-09-19 17:46 ` Ulrich Drepper
2007-09-19 17:57 ` Andi Kleen
2007-09-19 18:02 ` Ulrich Drepper
2007-09-19 18:30 ` Andi Kleen
2007-09-19 18:38 ` Rick Jones [this message]
2007-09-19 19:40 ` Andi Kleen
2007-09-19 20:33 ` Valdis.Kletnieks
2007-09-19 18:06 ` Alan Cox
2007-09-19 16:15 ` David Miller
2007-09-19 16:39 ` Alan Cox
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=46F16CC1.9090302@hp.com \
--to=rick.jones2@hp.com \
--cc=andi@firstfloor.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).