From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] Access through NAT
Date: Fri, 12 Aug 2011 10:21:45 -0700 [thread overview]
Message-ID: <391F0A47-638F-4793-93EF-CF6A23EC472C@orthanc.ca> (raw)
If you port forward the ticket port to your auth server and the
exportfs port to your CPU server, you should be able to 'import
nathost ...' from the wilds of the Internet.
As mentioned elsewhere, beware assinine five minute state timeouts in
the NAT implementation. Push aan onto the connection, or run a
background job that stats something across the mount every couple of
minutes.
next reply other threads:[~2011-08-12 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 17:21 Lyndon Nerenberg [this message]
2011-08-12 17:55 ` Charles Forsyth
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=391F0A47-638F-4793-93EF-CF6A23EC472C@orthanc.ca \
--to=lyndon@orthanc.ca \
--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).