From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 1488 invoked from network); 3 Jan 2022 21:11:16 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 3 Jan 2022 21:11:16 -0000
Received: from odoacer.turtle-trading.net ([93.241.193.16]) by 4ess; Mon Jan  3 15:53:05 -0500 2022
Received: from zenobia.turtle-trading.net ([192.168.2.111])
	by odoacer.turtle-trading.net with esmtp (Exim 4.80)
	(envelope-from <benny@turtle-trading.net>)
	id 1n4Tyi-00038l-UN; Mon, 03 Jan 2022 21:30:48 +0100
Received: from benny by zenobia.turtle-trading.net with local (Exim 4.94.2)
	(envelope-from <benny@turtle-trading.net>)
	id 1n4Tyi-000Uor-M9; Mon, 03 Jan 2022 21:30:48 +0100
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: hiro <23hiro@gmail.com>
Cc: 9front@9front.org
References: <87o84syh0s.fsf@turtle-trading.net>
	<CAFSF3XN8_i+e1PfvzSMrxJ=oMvNz7V=VY9v=pSEbKobYAw4bCA@mail.gmail.com>
Date: Mon, 03 Jan 2022 21:30:48 +0100
In-Reply-To: <CAFSF3XN8_i+e1PfvzSMrxJ=oMvNz7V=VY9v=pSEbKobYAw4bCA@mail.gmail.com>
	(hiro's message of "Mon, 3 Jan 2022 18:43:37 +0100")
Message-ID: <87y23w7e9z.fsf@turtle-trading.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: ISO-certified element dependency persistence-oriented controller 
Subject: Re: [9front] Loopback device
Reply-To: 9front@9front.org
Precedence: bulk

Hi hiro,

Thanks for taking the time.

hiro writes:
> loopback is a *link*. it has two sides.
> it's not the same as the 127.0.0.1 feature from other unixes.

Ok.  But that does not answer my questions.  Why doesn't the bind
command from the man page work?  And what *does* loopback do?

Calling it a link with two sides makes it sound like a pipe.  And being
mounted in /net makes it sound like, well, localhost, which also has two
sides, in the sense that I can run a server on it and than connect to
that server, all on the same host.

> localhost/127.0.0.1 is not normally used on plan9.
>
> it doesn't make much sense on a distributed and namespaced system.
> better use more meaningful unique IPs and hostnames and service names
> and then use just those, together with our excellent ndb service to
> resolve it all.

I find I most often use it for testing and for other code that needs an
IP with two sides where I do not want to hardcode, configure or find out
the host name or host IP.

Thanks, benny