On Nov 15, 2008, at 10:55 AM, Eric Van Hensbergen wrote:
Haven't run into this scenario before myself, so I'm not quite sure
how to get out of it.
I just installed a new virtual standalone CPU server on my home
machine. I followed the instructions on the wiki for standalone
cpu/auth.
I'm drawterming in this case from a windows box. I can drawterm in as
bootes, but when I try to drawterm in as my user account I get
cpu: cannot get auth tickets in p9sk1: The operation completed
successfully.
What step did I miss?
you /lib/ndb has the loopback interface and auth settings for your
virtual net?
I remember putting in something like the following on my VMWare
instance (:
ipnet=vmnet ip=192.168.254.0 ipmask=255.255.255.0
auth=vm
cpu=vm
fs=vm
bootf=/386/9pc
dns=192.168.254.2
dnsdom=YOURDOMAIN
authdom=YOURDOMAIN auth=vm
ip=192.168.254.105 sys=vm ether=VIRTETHER
dom=YOURDOMAIN
VMWare created it's NAT'd address on 192.168.254.X
So I also do the following to ease the pain:
[home:~] jas% cat `which cpu`
#!/usr/local/plan9/bin/rc
if(! ~ $#* 1){
echo 'usage: cpu <user>'
exit usage
}
drawterm -a 192.168.254.105 -c 192.168.254.105 -u $1
-jas
