Re: [9fans] help connect a terminal to kfs or Standalone CPU

Re: [9fans] help connect a terminal to kfs or Standalone CPU

[Russ Cox]

did you rename the auth files as directed in cpurc?

can you connect to the auth server using

	con -l 'tcp!$auth!ticket'
	(ctl-\, q will quit)

?

[9fans] help connect a terminal to kfs or Standalone CPU

[William Gunnells]

>how are you initializing your factotum?
>what does cat /mnt/factotum/ctl print
>if you run it on your cpu/auth server?

cat/mnt/factotum/ctl
reads
key dom='' proto=p9sk1 user=bootes !hex? !password?

When I boot the cpu/auth I normally don't enter
sectore password. I didn't think I needed it yet. This
was the default values for factotum. I didn't really
know how to edit this file other then echo a new value
with I think delkey or something.

My terminal bootdisk is bare. I just enter il, and
type in auth and fs which is 192.168.0.2 and try to
log in with the password I set with auth/changeuser
william.
I also executed auth/enable william.

> Still having trouble with terminal connection to
> CPU/Auth kfs.  Yes I did rename the files as stated
> in
>
> in cpurc. I did it manualy. Also I'm able to connect
> with
> con -l 'tcp!kfs!ticket'
> (ctl-\, q will quit)
>
> Very cool command its response was
> connected to tcp!kfs!ticket on /net/tcp/20
>
> So I suppose my ticket is fine. Here is the exact
> error I receive at terminal before it reboots
>
>
> authentication failed (auth_proxy fd: kfs system
> error
>
> ::connection rejected), trying mount anyways
> boot: /: authentication failed
> kernel


__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

Re: [9fans] help connect a terminal to kfs or Standalone CPU

[Russ Cox]

how are you initializing your factotum?
what does cat /mnt/factotum/ctl print
if you run it on your cpu/auth server?

[9fans] help connect a terminal to kfs or Standalone CPU

[William Gunnells]

UPDATE**
Still having trouble with terminal connection to
CPU/Auth kfs.  Yes I did rename the files as stated in

in cpurc. I did it manualy. Also I'm able to connect
with
con -l 'tcp!kfs!ticket'
(ctl-\, q will quit)

Very cool command its response was
connected to tcp!kfs!ticket on /net/tcp/20

So I suppose my ticket is fine. Here is the exact
error I receive at terminal before it reboots


authentication failed (auth_proxy fd: kfs system error

::connection rejected), trying mount anyways
boot: /: authentication failed
kernel
>
> Then the system just cycles through and reboots...
>
> Also used disk/kfscmd chat. I think its a ticket
> problem. Not sure how to correct it. Maybe I have
> something set up wrong.
>
> Here are my configs
>
> #!/bin/rc
> echo -n cpu > /env/service
> date > /env/boottime
>
> # replace FILESERVER with the name of your file
> server
> # here we start with kfs, your local disk file
> system
> fileserver=kfs
>
> # replace FACEDOM with the local domain to be used
> in
> the faces database
> facedom=FACEDOM
> for (i in '#m' '#i' '#S' '#t')
>         bind -a $i /dev >/dev/null >[2]/dev/null
>
> ip/ipconfig -g 192.168.0.1 ether /net/ether0
> 192.168.0.2 255.255.255.0
> # name translation, cs sets /dev/sysname
> ndb/cs
> sysname=`{cat /dev/sysname}
> sysname=kfs
> ndb/dns -r
>
> # parallelism for mk
> NPROC=`{wc -l /dev/sysstat}
> NPROC=`{echo $NPROC|sed 's/ .*//'}
>
> prompt=($sysname^'# ' ' ')
>
> # pick a timeserver closer to you when you can or
> we'll get clogged
> #aux/timesync plan9.bell-labs.com
>
> # uncomment the following for booting other systems
> ip/dhcpd
> ip/tftpd
>
> # If you are on an auth server, start these before
> listening:
> #
> auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null
> >[2=1]
> auth/cron >>/sys/log/cron >[2=1] &
> #
> # also rename some files:
> #
>  if(! test -e /rc/bin/service.auth/il566){
>        mv /rc/bin/service.auth/authsrv.il566
> /rc/bin/service.auth/il566
>        mv /rc/bin/service.auth/authsrv.tcp567
> /rc/bin/service.auth/tcp567
>        mv /rc/bin/service/il566
> /rc/bin/service/_il566
>        mv /rc/bin/service/tcp567
> /rc/bin/service/_tcp567
>  }
> # for standalone cpu only
> disk/kfscmd 'listen il!*!17008'
> # services available to networks
> aux/listen -q -d /rc/bin/service.auth -t
> /rc/bin/service il
> aux/listen -q -d /rc/bin/service.auth -t
> /rc/bin/service tcp
>
> and local
>
> database=
>         file=/lib/ndb/local
>         file=/lib/ndb/common
>
> ipnet=myipnet ip=192.168.0.0 ipmask=255.255.255.0
> ipgw=192.168.0.1
> auth=kfs
> proto=il
>
> ip=192.168.0.2 ether=00c04f182de5 sys=kfs
> bootf=/386/9pcauth
> proto=il
> ip=192.168.0.3 ether=009027626acc sys=term
> bootf=/386/9pc
> proto=il




__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

[9fans] help connect a terminal to kfs or Standalone CPU

[William Gunnells]

Having trouble getting a terminal to connect to
Standalone CPU. Used wiki resource but still no luck.
This is the error I receive:


authentication failed (auth_proxy rpc write
::connection rejected), trying mount anyways
boot: /: attach -- unknown user or failed
authentication

Then the system just cycles through and reboots...

Also used disk/kfscmd chat. I think its a ticket
problem. Not sure how to correct it. Maybe I have
something set up wrong.

Here are my configs

#!/bin/rc
echo -n cpu > /env/service
date > /env/boottime

# replace FILESERVER with the name of your file server
# here we start with kfs, your local disk file system
fileserver=kfs

# replace FACEDOM with the local domain to be used in
the faces database
facedom=FACEDOM
for (i in '#m' '#i' '#S' '#t')
        bind -a $i /dev >/dev/null >[2]/dev/null

ip/ipconfig -g 192.168.0.1 ether /net/ether0
192.168.0.2 255.255.255.0
# name translation, cs sets /dev/sysname
ndb/cs
sysname=`{cat /dev/sysname}
sysname=kfs
ndb/dns -r

# parallelism for mk
NPROC=`{wc -l /dev/sysstat}
NPROC=`{echo $NPROC|sed 's/ .*//'}

prompt=($sysname^'# ' ' ')

# pick a timeserver closer to you when you can or
we'll get clogged
#aux/timesync plan9.bell-labs.com

# uncomment the following for booting other systems
ip/dhcpd
ip/tftpd

# If you are on an auth server, start these before
listening:
#
auth/keyfs -wp -m /mnt/keys /adm/keys >/dev/null
>[2=1]
auth/cron >>/sys/log/cron >[2=1] &
#
# also rename some files:
#
# if(! test -e /rc/bin/service.auth/il566){
#       mv /rc/bin/service.auth/authsrv.il566
/rc/bin/service.auth/il566
#       mv /rc/bin/service.auth/authsrv.tcp567
/rc/bin/service.auth/tcp567
#       mv /rc/bin/service/il566
/rc/bin/service/_il566
#       mv /rc/bin/service/tcp567
/rc/bin/service/_tcp567
# }
# for standalone cpu only
disk/kfscmd 'listen il!*!17008'
# services available to networks
aux/listen -q -d /rc/bin/service.auth -t
/rc/bin/service il
aux/listen -q -d /rc/bin/service.auth -t
/rc/bin/service tcp

and local

database=
        file=/lib/ndb/local
        file=/lib/ndb/common

ipnet=myipnet ip=192.168.0.0 ipmask=255.255.255.0
ipgw=192.168.0.1
auth=kfs
proto=il

ip=192.168.0.2 ether=00c04f182de5 sys=kfs
        bootf=/386/9pcauth
        proto=il

ip=192.168.0.3 ether=009027626acc sys=term
        bootf=/386/9pc
        proto=il

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com