9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: john@csplan9.rit.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] terminals and /lib/ndb/local
Date: Tue, 15 Jan 2008 15:59:48 -0500	[thread overview]
Message-ID: <1edca2d4e0580cd525388aaa0b553556@csplan9.rit.edu> (raw)
In-Reply-To: <616705e79b4649f9f5e1418a6af0f867@quanstro.net>

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


  reply	other threads:[~2008-01-15 20:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 20:05 john
2008-01-15 20:44 ` erik quanstrom
2008-01-15 20:59   ` john [this message]
2008-01-15 21:10     ` erik quanstrom
2008-01-15 21:28       ` john
2008-01-16  0:11         ` john

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1edca2d4e0580cd525388aaa0b553556@csplan9.rit.edu \
    --to=john@csplan9.rit.edu \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).