9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 system behind firewall
Date: Wed, 26 Mar 2008 20:19:45 +0900	[thread overview]
Message-ID: <019b4d8a18ccf5b5ee8588951200206f@hera.eonet.ne.jp> (raw)
In-Reply-To: <ebccbb7588b05715d97b244c06a58d1c@hamnavoe.com>

Thank you very much, Richard.

> A long delay when connecting to a server behind a firewall may be an
> attempt to connect to the secstore port.

I'm not running secstore yet at the target (Plan 9-2) auth server.

> Can you configure the firewall to open tcp port 5356?

Yes, I can.
I'll try this soon.   I'm now in a very tough time schedules, because of
our comming new year, semester, here.

Our situation is as this figure.   Plan 9-1 and Plan 9-2 have local ip addresses,
say 192.168.1.xx for Plan 9-1, 192.168.50.xx for Plan 9-2.  Both firewall
machines have global ip addresses.

                                                          real wall
___________                                         || other building                         ____________
|    Plan 9-1   |==>Linux box's <=============>another firewall<=|   Plan 9-2        |
| (Ken's fs,      |         firewall             Univ  LAN            BB router             | venti+fossil+   |
| auth server, |                                                              MZK-40g??           | cpu server,      |
| cpu server,  |       other Debian                                                                | terminals         |
|terminals)    |            machines                                                                 |Debian, XP etc |
| Windows XP|                                                                                             _____________
-----------

Now attempting to reach from Plan 9-1 domain terminal to Plan 9-2 system.

One correction of my last mail:
I can boot Plan 9 terminal in the Plan 9-1 domain using Plan 9-2 file/auth
server.   It was just too long time than I can wait.    5.5 minutes from
boot the kernel to a factotum responce of Plan 9-2 server, and 5 more minutes
from it to get rio system (after type of password), total=10.5 minutes.
Yes, then, I judged it failed to bootup.   After the success of bootup,
there is no problem, and I can use the Plan 9 teminal as usual way.

I cannot solve this tommorow, Friday maybe.

Kenji



  reply	other threads:[~2008-03-26 11:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-24 11:50 kokamoto
2008-03-26  9:46 ` Richard Miller
2008-03-26 11:19   ` kokamoto [this message]
2008-03-26 15:33     ` john
2008-03-28 11:25     ` kokamoto
2008-03-25  1:27 erik quanstrom

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=019b4d8a18ccf5b5ee8588951200206f@hera.eonet.ne.jp \
    --to=kokamoto@hera.eonet.ne.jp \
    --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).