9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: kokamoto@hera.eonet.ne.jp, 9fans@9fans.net
Subject: Re: [9fans] Plan 9 system behind firewall
Date: Mon, 24 Mar 2008 21:27:30 -0400	[thread overview]
Message-ID: <f2ed48e92994fc034cf3f0294a83748a@coraid.com> (raw)

> I have two sets of Plan 9 system within different IP domain, one of which
> is sitting behind the firewall made by a brordband router and using fossil+venti+
> auth/cpu server and terminals(Plan 9-1).
> Another is using Ken's fs, standalone auth server, cpu server, and terminals
> (Plan 9-2).
[...]
> Lastly, I tried to login to the Plan 9-1 system behind the firewall from the above
> Plan 9-2 system, and now I have problem.   When I booted the Plan 9 kernel from
> floppy drive (the kernel was read from the Plan 9-2 standalone auth server),
> I had to wait 5 minutes until some response from the Plan 9-1
> auth server behind the firewall.  It asked password, and I typed it, then,
> I can reach the CPU server, not the Plan 9 system.  I suppose this is same as
> cpu command, and then, I have no display for rio.   ---fact 4

are Plan9-1 and Plan9-2 in different authentication domains?  if they
are not, this could explain fact 4.  you would have two auth servers serving
the same authentication domain.   this would explain how cpu could work
when a direct login does not if you also have trouble contacting the remote
authentication server but not the local one.  this would allow plan 9 to know
about the local auth server when drawterm may not.

the long timeouts are sound like dns lookup problems to me.  i generally
double-check my ndb entries in cases like this, especially the auth, ip, and
ipnet entries associated with the auth server.

	- erik


             reply	other threads:[~2008-03-25  1:27 UTC|newest]

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

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=f2ed48e92994fc034cf3f0294a83748a@coraid.com \
    --to=quanstro@coraid.com \
    --cc=9fans@9fans.net \
    --cc=kokamoto@hera.eonet.ne.jp \
    /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).