From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 3 machine / local & wan functionality
Date: Thu, 12 Dec 2002 10:49:16 +0100 [thread overview]
Message-ID: <b9d96c83b5499fcedf008c2e0b3c3d6d@plan9.escet.urjc.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 190 bytes --]
It sounds reasonable. Anyway, we here run without /alt.net, so
we have no need for a `trampoline'. If you can't get different real
ip addresses things can be different for you, though.
[-- Attachment #2: Type: message/rfc822, Size: 2150 bytes --]
From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] 3 machine / local & wan functionality
Date: Thu, 12 Dec 2002 09:14:33 +0000
Message-ID: <3627984449@snellwilcox.com>
Hi,
I am considering a full (3 machine) Plan9 system at home,
using an fs, a cpu/auth server and a terminal.
I also want to be able to be able to dual boot the terminal into NT
(for my other half) and to access the FS from work.
I am planning configure the cpu server as a gateway (with two
ether cards) and put a "trampoline" between /alt.net and /net for
http (NT used only for web browsing).
To access from work I would boot from a floppy (as described on the list)
and then mount the fs across the Internet.
Is this a sane idea?
Is this enough to give me the functionality
I want without being too vulnerable to being "hacked to death"?
-Steve
next reply other threads:[~2002-12-12 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 9:49 Fco.J.Ballesteros [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 9:14 steve.simon
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=b9d96c83b5499fcedf008c2e0b3c3d6d@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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).