9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rgr@sdf.lonestar.org (Rob Ristroph)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] NAT'ing a drawterm connection
Date: Thu, 28 Aug 2003 23:32:34 -0500	[thread overview]
Message-ID: <87smnlgk2l.fsf@rgristroph-austin.ath.cx> (raw)
In-Reply-To: <Pine.LNX.4.44.0308242324350.3501-100000@fbsd.cpsc.ucalgary.ca>

>>>>> "andrey" == andrey mirtchovski <mirtchov@cpsc.ucalgary.ca> writes:
andrey>
andrey> On Sun, 24 Aug 2003, andrey mirtchovski wrote:
>> ps: i've had the setup pasted in the original mail work for a year already
>> with any significant issues. there's also a NAT rule for the other way
>> around, but more often I leave people logged in to mount the auth server's
>> /net, which is outside the 192 network.
>>
andrey>
andrey> err, i meant 'without'. it just works.
andrey>
andrey> import plan9 /net /net works better :)

Using your lines it works a bit better; you can get as far as the grey
rio screen but bringing up the pull down menu to make a new rc window
crashes something.  It was someone else on the other end, so I don't
know the exact error message.

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
?

In the meantime, I decided to try to achieve the same ends at drawterm
using vnc.  Disregarding port forwarding, when the Plan 9 and Linux
machines are directly on the same subnet with no router between them,
I can vnc from Plan 9 to Linux but on Linux I cannot connect a
vncviewer to the Plan 9 server.

On Plan 9 I start the server with the command "vncs -v".

On Linux, xvncviewer prints this and exits (never asked for a
password, as it did when I connected from Plan 9 to Linux):

VNC server supports protocol version 3.3 (viewer 3.3)
xvncviewer: VNC server closed connection

On Plan 9, I see this:

192.168.1.18# vncs -v
192.168.1.18# geometry is 1024x768
server started on display :3
announced in /net/tcp/27
call in /net/tcp/28
[550] 192.168.1.1!4719 /net/tcp/28: handshake
server version: RFB 003.003
client version: RFB 003.003
[550] 192.168.1.1!4719 /net/tcp/28: auth
vncs: vncchal: auth server protocol botch

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 ?

Thanks in advance,

--Rob


  parent reply	other threads:[~2003-08-29  4:32 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 [this message]
2003-08-29  4:50           ` andrey mirtchovski
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=87smnlgk2l.fsf@rgristroph-austin.ath.cx \
    --to=rgr@sdf.lonestar.org \
    --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).