[9fans] terminals and /lib/ndb/local

[john@csplan9.rit.edu]

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?
Thanks

John

/lib/ndb/local:

#
#  files comprising the database, use as many as you like, see ndb(6)
#
database=
	file=/lib/ndb/local
	file=/lib/ndb/common

auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
auth=csplan9.rit.edu authdom=rit.edu

auth=out9auth.cs.bell-labs.com authdom=cs.bell-labs.com

sys=go dom=go.cs.bell-labs.com
sys=outfs dom=out9auth.cs.bell-labs.com

sys=csplan9 dom=csplan9.rit.edu


authdom=ca.sandia.gov auth=plan9

ipnet=9net ip=192.168.18.0 ipmask=255.255.255.0
	fs=plan9.ca.sandia.gov
	cpu=plan9.ca.sandia.gov
	auth=plan9.ca.sandia.gov
	ipgw=192.168.18.10
	dnsdomain=ca.sandia.gov
	dns=192.168.18.10
	dns=146.246.250.1

# CPU server
sys=plan9 dom=plan9.ca.sandia.gov
	auth=plan9.ca.sandia.gov

# Linux laptop
sys=ramac ip=192.168.18.179 ether=001641e0fcfd

# Net-booting terminal
sys=gnot ether=001b210f7faa
	ip=192.168.18.90
	dom=gnot.ca.sandia.gov
	bootf=/386/9pxeload
	authdom=ca.sandia.gov

# John's terminal (with disk, root from tcp)
sys=jerq ether=001b210eaab5
	auth=plan9.ca.sandia.gov
	dom=jerq.ca.sandia.gov
	ipgw=192.168.18.10
	authdom=ca.sandia.gov

#Note this is wrong but ron is too lazy to fix it just yet.
sys=blit ether=ff1b210f7faa
	ip=192.168.18.92
	ipgw=192.168.18.10
	dom=gnot.ca.sandia.gov
	bootf=/386/9pxeload
	authdom=ca.sandia.gov

# Testbed
sys=ppc ether=0002b5019094
	ip=192.168.18.91
	dom=ppc.ca.sandia.gov
	bootf=/power/9eval.elf
	authdom=ca.sandia.gov

#
#  because the public demands the name localsource
#
ip=127.0.0.1 sys=localhost dom=localhost
smtp=plan9