From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] drawterm through nat
Date: Mon, 2 Feb 2004 21:52:45 +0100 [thread overview]
Message-ID: <02c801c3e9ce$83c0a0c0$67844051@SOMA> (raw)
In-Reply-To: <020df30b78a8c8a873288882c6a93aae@mteege.de>
> is it possible to drawterm to my nated home plan9
> network?
yes, afaik. it's just tcp.
> I have access to the nat gateway and
> can setup port forwarding. Which ports are needed
> for drawterm?
up in the 17000 range, but i'm too tired/lazy to check.
> Is the connection encrypted?
no, but the authentication is. tcp-hijacking [hi ECHELON]
is doable, but kinda impractical.
it's pretty impressive (save for those stupid 'postnote' windows
which essentially say 'bust'). it's a bit unforgiving when net delays
are exceeded. i've drawtermed from sydney to NY and paris to NY.
i'd like to re-write it in limbo, but my list of things i'd like to do
is getting rather long ...
next prev parent reply other threads:[~2004-02-02 20:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 13:44 Matthias Teege
2004-02-02 13:56 ` plan9
2004-02-02 20:52 ` boyd, rounin [this message]
2004-02-02 14:09 steve-simon
2004-02-02 18:46 Skip Tavakkolian
2004-02-02 18:02 ` andrey mirtchovski
2004-02-02 18:54 Skip Tavakkolian
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='02c801c3e9ce$83c0a0c0$67844051@SOMA' \
--to=boyd@insultant.net \
--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).