From mboxrd@z Thu Jan  1 00:00:00 1970
From: rgr@sdf.lonestar.org (Rob Ristroph)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The 9grid.
References: <11f199405b3be80ed1682181c3d10415@plan9.bell-labs.com>
In-Reply-To: <11f199405b3be80ed1682181c3d10415@plan9.bell-labs.com>
Message-ID: <87vfsw87kz.fsf@rgristroph-austin.ath.cx>
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 17 Aug 2003 13:25:32 -0500
Topicbox-Message-UUID: 1c8783c2-eacc-11e9-9e20-41e7f4b1d025

>>>>> "David" == David Presotto <presotto@closedmind.org> writes:
David>
David> If the two machines have fixed addresses there's no reason to
David> use dns at all.
David>
David> You should have a /lib/ndb/local that lists the network with
David> the appropriate auth server and fs server.  For example:
David>
David> ipnet=robsnet ip=199.199.9.0
David> 	ipgw=199.199.9.1
David> 	fs=199.199.9.2
David> 	auth=199.199.9.3

Here is what my /lib/ndb/local loks like right now:

#
#  files comprising the database, use ad many as you like, see ndb(6)
#
database=
    file=/lib/ndb/local
    file=/lib/ndb/common

ipnet=robsnet ip=192.168.0.0
    ipgw=192.168.1.1
    fs=192.168.1.17
    auth=192.168.1.18

#auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
authdom=robsnet

I think the last line is not needed.

When I then reboot the machine from the pcauth kernel, and then on a
linux machine run this command:

./drawterm-linux -c 192.168.1.18 -a 192.168.1.18

I get the drawterm prompt in the drawterm window:

user[none]: rgr
password:

but after I type my password, I get this message at the linux command
line, and the drawterm seems to freeze up:

./drawterm-linux: cannot authenticate with p9
abort 4035

On the Plan 9 computer, the last few lines of /sys/log/auth look like
this:

192.168.1.18 Aug 17 09:13:18 keyfs starting warning: 3f3f7f6e
              3f3e2b9a
192.168.1.18 Aug 17 09:13:18 tr-ok rgr@rgr(192.168.1.1) -> rgr@rgr
192.168.1.18 Aug 17 09:13:18 tr-ok rgr@rgr(192.168.1.1) -> rgr@bootes

Any suggestions as to what I should check next ?

--Rob