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 17233 invoked from network); 14 Jan 2021 12:26:49 -0000
Received: from 1ess.inri.net (216.126.196.35)
  by inbox.vuxu.org with ESMTPUTF8; 14 Jan 2021 12:26:49 -0000
Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Thu Jan 14 06:47:32 -0500 2021
Message-ID: <ECDFF51BD1295A573F1D5EE05090DBE8@felloff.net>
Date: Thu, 14 Jan 2021 12:47:16 +0100
From: cinap_lenrek@felloff.net
To: 9front@9front.org
In-Reply-To: <724ACFC5-D66E-4028-AC69-648A7CF0D921@me.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: object-oriented NoSQL configuration XMPP over SVG persistence descriptor polling manager 
Subject: Re: [9front] tsl boot, tsl error
Reply-To: 9front@9front.org
Precedence: bulk

the t9fs service basically just establishes a tls tunnel,
authenticated using your dp9ik key, and then proxies to
the 9fs service on the fileserver.

here, take a look:

term% cat /rc/bin/service/tcp17020
#!/bin/rc
exec tlssrv -A /bin/aux/trampoline 'net!$fs!9fs'

so this implies that your fileserver is also listed in
ndb with a fs= attribute in the ipnet or the cpu server
ip entry.

and, that the fileserver is listening on the 9fs
(tcp port 564).

you can test if your fs is listening by dialing
the 'net!$fs!9fs' dialstring. (note here, $fs is
*NOT* a environment variable, it is a ndb attribute
that ndb/cs will search for (relative to the machines
ip address) and substitute it by the value).

--
cinap