From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file?
Date: Wed, 10 Mar 2021 10:07:09 -0700 [thread overview]
Message-ID: <f6093b54-465d-5921-9a0a-87a2fc12f1d5@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <3035421.5fSG56mABF@lenovo.localdomain>
On 3/10/21 9:38 AM, Michael wrote:
> I always thought the localhost class A addresses were from days of old
> 'inter- network' era. The difference with 127.0.0.1 and a private
> LAN address is the 127.0.0.1 does not reach the data link layer,
> but loops-back at IP layer 3 and responds to any applications on the
> local PC. So, I understood this to mean it never went through the
> whole network stack, as it does when you ping a remote host.
The 127/8 (formerly called a class A) network is reserved / allocated
for a host to communicate with itself.
However, /how/ local addresses are used is entirely implementation
specific. This goes for both 127.0.0.1 and other addresses bound to
local network cards.
Linux will not send traffic to the local LAN IP to the NIC either. But
that's a /Linux/ /implementation/ detail. Other OSs, e.g. Windows,
don't use a loopback adapter for 127.0.0.1. Instead it's purely a
software construct. But that's a /Windows/ /implementation/ detail.
Aside: Windows (2k and onward) does have a loopback adapter that you
can optionally install. However you /can't/ assign 127.0.0.1 (or any
127/8) to it. It is meant to be used like Linux uses the dummy adapter.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2021-03-10 17:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 22:23 [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file? Grant Taylor
2021-02-22 6:20 ` Andrew Udvare
2021-02-25 2:37 ` Peter Humphrey
2021-02-25 2:50 ` Grant Taylor
2021-02-25 7:02 ` Arve Barsnes
2021-02-25 7:33 ` Grant Taylor
2021-03-10 5:09 ` Grant Taylor
2021-03-10 13:27 ` Mark Knecht
2021-03-10 15:25 ` Michael
2021-03-10 16:00 ` Mark Knecht
2021-03-10 16:38 ` Michael
2021-03-10 17:07 ` Grant Taylor [this message]
2021-03-10 17:01 ` Grant Taylor
2021-03-10 16:58 ` Grant Taylor
2021-03-11 13:38 ` Michael
2021-03-11 16:50 ` Grant Taylor
2021-03-12 19:04 ` Michael
2021-03-13 19:01 ` Grant Taylor
2021-03-16 12:16 ` Michael
2021-03-16 12:33 ` Peter Humphrey
2021-03-16 18:54 ` Grant Taylor
2021-03-11 17:04 ` Grant Taylor
2021-03-10 16:44 ` Grant Taylor
2021-03-10 17:43 ` Mark Knecht
2021-03-10 18:37 ` Grant Taylor
2021-03-11 10:54 ` Wols Lists
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=f6093b54-465d-5921-9a0a-87a2fc12f1d5@spamtrap.tnetconsulting.net \
--to=gtaylor@gentoo.tnetconsulting.net \
--cc=gentoo-user@lists.gentoo.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