From: John Darrington <john@darrington.wattle.id.au>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Contents of /etc/hosts
Date: Sun, 9 Oct 2016 11:56:36 +0200 [thread overview]
Message-ID: <20161009095635.GA22834@jocasta.intra> (raw)
In-Reply-To: <57FA0A1A.7040905@crazy-compilers.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
On Sun, Oct 09, 2016 at 11:12:58AM +0200, Hartmut Goebel wrote:
Am 08.10.2016 um 16:08 schrieb John Darrington:
> > 127.0.0.2 gambrinus
> Now what happens if you "ping gambrinus"?
>
> ICMP packets will be sent to the local host.
Me fool. of course it does: the loopback interface has netmask /8
)defined in RFC 990 https://tools.ietf.org/html/rfc990
But for IPv6 the loopback interface has ::1/128, this ::2 would not got
there.
So if we follow your proposal adding "127.0.0.2 gambrius" to /etc/hosts,
we could not contently doe this for IPv6.
IPv6 is something I'm not really familiar with. Presumably there is an
equivalent way to do this in IPv6 ?
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-10-09 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 18:31 Contents of /etc/hosts John Darrington
2016-10-05 20:17 ` Ludovic Courtès
2016-10-06 0:57 ` John Darrington
2016-10-06 10:07 ` Hartmut Goebel
2016-10-08 14:19 ` John Darrington
2016-10-11 20:25 ` Ludovic Courtès
2016-10-06 9:24 ` Hartmut Goebel
2016-10-08 14:08 ` John Darrington
2016-10-09 9:12 ` Hartmut Goebel
2016-10-09 9:56 ` John Darrington [this message]
2016-10-09 10:53 ` Hartmut Goebel
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=20161009095635.GA22834@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.