9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ingo Krabbe <ikrabbe.ask@gmail.com>
To: <9fans@9fans.net>
Subject: Re: [9fans] Remote auth server
Date: Mon, 24 Mar 2014 14:53:46 +0100	[thread overview]
Message-ID: <48053adc240ee5db09a06caec3e83519@krabbe.dyndns.org> (raw)
In-Reply-To: <CAOotBeL=pVM9nGiae3aOHe_F9WnB-_kUaj3JdVJmPuk_HF4faw@mail.gmail.com>

Yes it is possible and usefull too. All you should have on a fast lan is a fileserver.
But:
	1. the plan9 terminal must configure the network before it connects to the auth server either through dhcp or through a static configuration in the boot configuration
	2. somewhere in the setup of the terminal or the auth server you have to use a hostname that goes into the nvram, that can be reached at boot time. I can't remember where it was, but it was one of my bigger struggles with the plan9 setup.



> Hi!
>
> I'm trying to setup my first multi-host Plan 9 system.
> I was thinking about running file server/auth server on a VPS so that
> I can access it from anywhere.
>
> I configured cpu service on my VPS and I can connect to it via
> drawterm. But when I try to boot a terminal that is configured to use
> it as auth server, the terminal stops with a message:
> mount: auth_proxy: authread: auth protocol not finished.
>
> But is it actually possible to have the auth server and terminal not
> on the same LAN? Every configuration example I've seen has all the
> resources on the same IP address block.
>
> Thanks!
>
> --
>    Paul Anokhin





  reply	other threads:[~2014-03-24 13:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 13:35 Paul A. Anokhin
2014-03-24 13:53 ` Ingo Krabbe [this message]
2014-03-24 14:11   ` cinap_lenrek
2014-03-24 14:16     ` erik quanstrom
2014-03-24 14:09 ` erik quanstrom
2014-03-24 15:41   ` Paul A. Anokhin
2014-03-24 16:34     ` erik quanstrom

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=48053adc240ee5db09a06caec3e83519@krabbe.dyndns.org \
    --to=ikrabbe.ask@gmail.com \
    --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).