9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NAT'ing a drawterm connection
Date: Thu, 28 Aug 2003 22:50:12 -0600	[thread overview]
Message-ID: <Pine.LNX.4.44.0308282236220.28989-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <87smnlgk2l.fsf@rgristroph-austin.ath.cx>

On 28 Aug 2003, Rob Ristroph wrote:

> Suppose in your "import" command that "plan9" isn't a machine running
> Plan 9 but another computer that can see the plan9 computer.  Can you
> forward some set of ports to make it work, or are you just out of luck
> ?

import expects exportfs to be running on the other side. it should be fine
by just redirecting the exportfs port. if that's what you want to achieve.

> client version: RFB 003.003
> [550] 192.168.1.1!4719 /net/tcp/28: auth
> vncs: vncchal: auth server protocol botch

in my case that usually means i've gotten the authdoms in /lib/ndb/local on
the auth server wrong. can you cpu from the same machine to itself? try that
with 'auth/debug' and see what's wrong.

> Nothing seems to be printed in /sys/log/auth.  If I run a vnc server
> on linux, I have to set a password; have I not done the equivalent on
> Plan 9 ?  How do I do it ?

you do not, vncs is smart enough to use the password already set for the
user on the auth server. do you have a password set?

another thing, suggested some time ago by Geoff Collyer -- cd /adm/keys on
the console of the auth server and type 'ls' -- if you see valid user names
for the system you're ok, of not, the nvram on the system doesn't contain
the proper password to decode the password..

but: my auth server was set a few months ago, so i may be out of sync...

andrey




  reply	other threads:[~2003-08-29  4:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-25  4:00 Rob Ristroph
2003-08-25  4:04 ` andrey mirtchovski
2003-08-25  5:15   ` Rob Ristroph
2003-08-25  5:22     ` andrey mirtchovski
2003-08-25  5:26       ` andrey mirtchovski
2003-08-25 12:35         ` Bruce Ellis
2003-08-25 13:11           ` [9fans] " Jim Choate
2003-08-25 13:18             ` andrey mirtchovski
2003-08-25 14:00               ` Jim Choate
2003-08-25 15:24                 ` andrey mirtchovski
2003-08-25 15:46                   ` Scott Schwartz
2003-08-25 15:55                     ` andrey mirtchovski
2003-08-25 17:40                     ` Jim Choate
2003-08-25 16:05             ` matt
2003-08-25 17:37               ` Jim Choate
2003-08-26 11:22                 ` matt
2003-08-28  0:13                   ` Bruce Ellis
2003-08-28  8:21                     ` matt
2003-08-25 13:18           ` [9fans] " Russ Cox
2003-08-25 14:02             ` [9fans] " Jim Choate
2003-08-25 17:52             ` [9fans] " Bruce Ellis
2003-08-26  0:30               ` boyd, rounin
2003-08-28  3:23               ` Russ Cox
2003-08-29  4:32         ` Rob Ristroph
2003-08-29  4:50           ` andrey mirtchovski [this message]
2003-08-25 14:53     ` matt
2003-08-26  1:16 Skip Tavakkolian
2003-08-26  1:50 ` boyd, rounin
2003-08-26  4:25   ` Jim Choate
2003-08-26  4:17 ` Jim Choate
2003-08-29  4:39 YAMANASHI Takeshi

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=Pine.LNX.4.44.0308282236220.28989-100000@fbsd.cpsc.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).