9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: csant <csant@csant.info>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] authdial: unknown host
Date: Wed, 28 Jun 2006 22:15:22 +0200	[thread overview]
Message-ID: <op.tbvg7wvxd84skq@fiore.malebolge> (raw)
In-Reply-To: <op.tbvdv8q8d84skq@fiore.malebolge>

> trying to mount a Plan 9 machine from Linux.
>
> I tell /srv/fscons to listen on ports 564 (tcp) and 17008 (il). I
> 	% auth/factotum -g 'proto=p9sk1 user=me dom=mydomain !password=mypw'
> and then on the Linux box I try to establish a preauthenticated  
> connection (following instructions from this list a few weeks ago):
>
> 	$ srv -a 10.0.0.5 plan9
> 	!adding key: role=client proto=p9sk1 dom=mydomain
> 	user[me]: me
> 	password:
> 	!
> 	authdial: unknown host mydomain
>
> I am a bit confused by the last error message: how come authdial treats  
> mydomain as the host? Where have I misconfigured stuff?
>
> 	$ hostname -f
> 	linux.mydomain
> seems to tell me that (at least the Linux box) knows about the domain.
>
> Needless to say, when I
> 	# mount -t 9p -o proto=tcp 10.0.0.5 /mnt/9/
> 	mount: permission denied
> since it was trying to "attach main as nobody: connection not  
> authenticated, not console".
>
> Any pointer please to how I could get this to work?

I got one step further:

Added the following lines to $PLAN9/ndb/local :
	authdom=mydomain
         auth=plan9
where plan9 is the (only) Plan 9 machine on this network.

But now I get
	$ srv -a 10.0.0.5 plan9
	!adding key: role=client proto=p9sk1 dom=mydomain
	user[me]: me
	password:
	!
	authdial: Connection refused
	srv: authproxy: auth_proxy rpc: no rpc pending

/c


  reply	other threads:[~2006-06-28 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 19:03 csant
2006-06-28 20:15 ` csant [this message]
2006-06-28 21:02   ` csant

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=op.tbvg7wvxd84skq@fiore.malebolge \
    --to=csant@csant.info \
    --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).