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

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

[john]

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

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

[erik quanstrom]

> 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

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

[john]

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


Sorry, I didn't specify. plan9 is the auth server; csplan9 is my machine
at RIT.
Ron just discovered that somewhere in my recent changes I make drawterm
stop working; I'm sure that's got something to do with the cpu problems. I've
since done "yesterday" and pulled in a working version, so now here's what
we're using:

#
#  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=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
	cpu=plan9
	auth=plan9
	ipgw=192.168.18.10
	authdom=ca.sandia.gov

sys=plan9 dom=plan9.ca.sandia.gov

sys=ramac ip=192.168.18.179 ether=001641e0fcfd

sys=gnot ether=001b210f7faa
	ip=192.168.18.90
#	ipgw=192.168.18.10
	dom=gnot.ca.sandia.gov
	bootf=/386/9pxeload
	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

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

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

[erik quanstrom]

> Sorry, I didn't specify. plan9 is the auth server; csplan9 is my machine
> at RIT.
> Ron just discovered that somewhere in my recent changes I make drawterm
> stop working; I'm sure that's got something to do with the cpu problems. I've
> since done "yesterday" and pulled in a working version, so now here's what
> we're using:
> 
> auth=sources.cs.bell-labs.com	authdom=outside.plan9.bell-labs.com
> auth=out9auth.cs.bell-labs.com	authdom=cs.bell-labs.com
> auth=csplan9.rit.edu		authdom=rit.edu
> auth=plan9			authdom=ca.sandia.gov
>
> sys=go dom=go.cs.bell-labs.com
> sys=csplan9 dom=csplan9.rit.edu
> 

since you say
	sys=csplan9 dom=csplan9.rit.edu
then you say
	auth=csplan9.rit.edu authdom=rit.edu
i'm pretty sure you've declared that csplan9 is its own
authentication server.

- erik

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

[john]

>> Sorry, I didn't specify. plan9 is the auth server; csplan9 is my machine
>> at RIT.
>> Ron just discovered that somewhere in my recent changes I make drawterm
>> stop working; I'm sure that's got something to do with the cpu problems. I've
>> since done "yesterday" and pulled in a working version, so now here's what
>> we're using:
>> 
>> auth=sources.cs.bell-labs.com	authdom=outside.plan9.bell-labs.com
>> auth=out9auth.cs.bell-labs.com	authdom=cs.bell-labs.com
>> auth=csplan9.rit.edu		authdom=rit.edu
>> auth=plan9			authdom=ca.sandia.gov
>>
>> sys=go dom=go.cs.bell-labs.com
>> sys=csplan9 dom=csplan9.rit.edu
>> 
> 
> since you say
> 	sys=csplan9 dom=csplan9.rit.edu
> then you say
> 	auth=csplan9.rit.edu authdom=rit.edu
> i'm pretty sure you've declared that csplan9 is its own
> authentication server.
> 
> - erik

Yeah, it is. It's a cpu/auth/file server sitting at RIT. I shouldn't even have
included that in my mail, since it's not very important to the problem.
Basically, csplan9 is in there because I want to use it. Nobody else here
has an account on it or ever connects.

John

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

[john]

>>> Sorry, I didn't specify. plan9 is the auth server; csplan9 is my machine
>>> at RIT.
>>> Ron just discovered that somewhere in my recent changes I make drawterm
>>> stop working; I'm sure that's got something to do with the cpu problems. I've
>>> since done "yesterday" and pulled in a working version, so now here's what
>>> we're using:
>>> 
>>> auth=sources.cs.bell-labs.com	authdom=outside.plan9.bell-labs.com
>>> auth=out9auth.cs.bell-labs.com	authdom=cs.bell-labs.com
>>> auth=csplan9.rit.edu		authdom=rit.edu
>>> auth=plan9			authdom=ca.sandia.gov
>>>
>>> sys=go dom=go.cs.bell-labs.com
>>> sys=csplan9 dom=csplan9.rit.edu
>>> 
>> 
>> since you say
>> 	sys=csplan9 dom=csplan9.rit.edu
>> then you say
>> 	auth=csplan9.rit.edu authdom=rit.edu
>> i'm pretty sure you've declared that csplan9 is its own
>> authentication server.
>> 
>> - erik
> 
> Yeah, it is. It's a cpu/auth/file server sitting at RIT. I shouldn't even have
> included that in my mail, since it's not very important to the problem.
> Basically, csplan9 is in there because I want to use it. Nobody else here
> has an account on it or ever connects.
> 
> John

Ok, I think I've solved the problem. I hadn't given an IP for plan9, which
was a relic from before the server had a static IP. Giving it a static IP
makes everything seem to work; my current local file is appended,
although it still probably has some unneeded things in it.

John

#
#  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=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
#	authdom=ca.sandia.gov
	dns=192.168.18.10
	dns=140.246.250.1

sys=plan9 dom=plan9.ca.sandia.gov ip=192.168.18.13
	dom=plan9.ca.sandia.gov
	auth=plan9.ca.sandia.gov

sys=ramac ip=192.168.18.179 ether=001641e0fcfd

sys=gnot ether=001b210f7faa
	ip=192.168.18.90
#	ipgw=192.168.18.10
	dom=gnot.ca.sandia.gov
	bootf=/386/9pxeload
	authdom=ca.sandia.gov

sys=jerq ether=001b210eaab5 ip=192.168.18.93
	dom=jerq.ca.sandia.gov
	auth=plan9.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

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