From: sirjofri <sirjofri+ml-9fans@sirjofri.de>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] building a grid at university
Date: Fri, 30 Sep 2022 15:09:10 +0200 (GMT+02:00) [thread overview]
Message-ID: <2e21440d-13f4-47af-9f5d-1073459f2aa3@sirjofri.de> (raw)
In-Reply-To: <bBlnyF_bsKfyGVCYaFfZd6bFc4H-81jS2X5PfY6UekRKEYdZG7-naTV4yG0jzyFoIffOm2X-QqarVuJbm35Rnk1ov4I7-N-ZBv8QLwBm_20=@protonmail.com>
30.09.2022 12:42:53 Glenn Holmer via 9fans <9fans@9fans.net>:
> This has always seemed miraculous to me. Can you give an example of the commands?
On 9front:
rimport myserver /net
Communication basically always goes through the network interface present in /net (or /net.alt, depending on the software and configuration), so all network listeners you run after importing the /net of the server will just start listening on the network interface of the server. That's the power of namespaces for you.
Iirc with listen(8) you can set which network directory you want to listen on, so you can (for example) import the server /net to your local /net.alt and then start listening on /net.alt.
Btw this is also the easiest way to make a VPN-like bridge: import /net of the server, then start webfs for browsing, then all traffic this webfs process produces will be tunneled through the (tls-encrypted) 9p connection to the server.
sirjofri
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T75d22acfa474b209-Mf16010904898f92091ec20d8
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-09-30 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 22:33 type9freak
2022-09-28 7:02 ` sirjofri
2022-09-28 21:57 ` fig
2022-09-28 22:16 ` sirjofri
2022-09-30 1:28 ` fig
2022-09-30 2:59 ` ori
2022-09-30 6:30 ` sirjofri
2022-09-30 10:42 ` Glenn Holmer via 9fans
2022-09-30 13:09 ` sirjofri [this message]
2022-10-01 5:42 ` denzuko
2022-10-01 6:32 ` sirjofri
2022-10-01 6:44 ` denzuko
2022-10-01 6:44 ` denzuko
2022-09-28 20:21 ` Brian Hancock
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=2e21440d-13f4-47af-9f5d-1073459f2aa3@sirjofri.de \
--to=sirjofri+ml-9fans@sirjofri.de \
--cc=9fans@9fans.net \
/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).