9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robby <rtr@blueyonder.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] Drawterm or VMWare terminal?
Date: Thu, 27 Feb 2003 09:35:04 +0000	[thread overview]
Message-ID: <fi77a.7769$g77.61994124@news-text.cableinet.net> (raw)

Hi,

I am wondering if it is worthwhile to boot a VMWare Plan 9 at work
from my home network or if using drawterm is better.

I have a CPU/Auth server sitting in my home network behind a NAT
router with port forwarding (Netgear RT311). At the moment I am
forwarding ports 567 and 17013 to the CPU/Auth server and I can use
drawterm on my NT box at work to connect.

I have also started playing with VMWare. Would it be sensible to boot
a proper terminal across the long wires of the internet? Which ports
would I need to forward and how much does that open my local home
network up to the world?

As far as I can see, two options are available for running the
terminal under VMWare: 1. Boot a VMWare local 9pc kernel, but take the
root from il. 2. Get the kernel from my home server as well.

With just the two ports 567 and 17013 forwarded, I can't get the
VMWare kernel to connect to my home server. At the question "root is
from (il, local):" I type "il", and then get asked about my filesystem
and auth server IP addresses, to which I provide the IP address to my
router. I then get a "boot: can't connect to file server: protocol
unreachable" error.

Thanks for any help,
Robby


             reply	other threads:[~2003-02-27  9:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  9:35 Robby [this message]
2003-02-27 14:42 ` Russ Cox
2003-02-27 14:49   ` Dan Cross
2003-02-27 14:54     ` Russ Cox
2003-02-27 15:11       ` Dan Cross
2003-02-27 15:19         ` Russ Cox
2003-02-27 15:49           ` Dan Cross
2003-02-27 15:57             ` rob pike, esq.
2003-02-27 15:59               ` Dan Cross
2003-02-27 16:04                 ` Boyd Roberts

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='fi77a.7769$g77.61994124@news-text.cableinet.net' \
    --to=rtr@blueyonder.co.uk \
    --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).