From: vdharani@infernopark.com
To: "Vester Thacker" <vester.thacker@gmail.com>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Best option for a Plan 9 gateway.
Date: Sun, 26 Sep 2004 13:19:48 -0500 [thread overview]
Message-ID: <59349.192.11.226.116.1096222788.squirrel@www.infernopark.com> (raw)
In-Reply-To: <32a656c204092605592a08d66@mail.gmail.com>
> What is the best option for building a Plan 9 gateway? Does a Plan 9
> gateway machine need to be an authentication server? Or can any server
> be a gateway as long as it has 2 NICs? I'm curious to how others have
> solved the problem. Thanks in advance.
gateway machine need not be an auth server. also, in principle, even one
NIC should be enough (in which case, it is an one-armed router) and i
think plan 9 will also work that way.
thanks
dharani
prev parent reply other threads:[~2004-09-26 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 12:59 Vester Thacker
2004-09-26 18:19 ` vdharani [this message]
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=59349.192.11.226.116.1096222788.squirrel@www.infernopark.com \
--to=vdharani@infernopark.com \
--cc=9fans@cse.psu.edu \
--cc=vester.thacker@gmail.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.
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).