> The reason I ask is that I missed that step the first time I tried to
> set up the CPU/Auth server, but I've since gone through it all again
> carefully more than once, and I stll get "connection rejected" with
> my Ken's file server. (Yes I know fossil/venti is the current
> standard, but what can I say, I'm, perhaps irrationally, or at least
> non-rationally, attached to the old file server.)
"connection rejected" is a message the file server prints
in the IL stack. I believe it has nothing to do with
authentication, but I also don't know what the criteria
are for rejection.
You can test connectivity using aux/9pcon:
cpu% aux/9pcon -n tcp!web.mit.edu!9fs
aux/9pcon: dial: connection refused
cpu%
If it does connect (which I doubt), you can try starting
a 9P session:
cpu% aux/9pcon -n tcp!sources.cs.bell-labs.com!9fs
Tversion 8192 9P2000
-> Tversion tag 65535 msize 8192 version '9P2000'
<- Rversion tag 65535 msize 8192 version '9P2000'
Tattach 1 -1 rsc ''
-> Tattach tag 3 fid 1 afid -1 uname rsc aname
<- Rattach tag 3 qid (0000000000000002 0 d)
cpu%
9pcon has no prompt; I typed the Tversion and Tattach lines.
Your server will probably reply to the Tattach with an Rerror;
sources is special.
Russ
