> We have a cpu/auth/file server here and a few terminals, one pxe booting
> and one standalone that I boot from tcp. I have things set up to the point
> where I am booting fine, can access the file system, etc. I can connect
> to remove cpu servers, but the strange thing is that I can't connect to my
> own cpu server. I think it's probably a problem with /lib/ndb/local...
> can you guys take a look at my configuration and tell me if you see any
> problems?
i assume your auth server is csplan9. it needs an ip address.
i notice that most of your machines declare that they are in
authdom ca.sandia.gov. this means they would authenticate to
"plan9" and not "csplan9".
here's how i set up my home network. hopefully
this helps.
#
# dns mumble ommited. the authdom is not well chosen.
#
auth=ladd.quanstro.net authdom=plan9.quanstro.net
ipnet=athensnat ip=192.168.0.0 ipmask=/120
fs=buda.quanstro.net
ipgw=192.168.0.4
gw=dexter-peak.quanstro.net
dns=192.168.0.136
dnsdomain=quanstro.net
authdom=plan9.quanstro.net
auth=ladd
cpu=ladd
# fileserver
ip=192.168.0.139 sys=buda
dom=buda.quanstro.net
# auth server.
ip=192.168.0.136 sys=ladd
dom=ladd.quanstro.net
dom=www.quanstro.net
authdom=plan9.quanstro.net
ip=192.168.0.54 sys=athens ether=000024c12c18
dom=athens.quanstro.net
authdom=plan9.quanstro.net
bootf=/386/9pxesokris
ip=192.168.0.56 sys=encampment ether=000347000cac
dom=encampment.quanstro.net
bootf=/386/9brom2
# terminal.
ip=192.168.0.57 sys=brasstown ether=0019dbb39287
ether=001b21028754
dom=brasstown.quanstro.net
bootf=/386/9brom2
- erik
