Hi group, I need help configuring a plan9 server (auth+dns+dhcp+fs).
I already have a plan9 system with /lib/ndb/local, /cfg/$sysname/cpurc
configured as per the wiki and other net sources. I compiled the
pccpuf kernel with no problems and declared it at /n/9fat/plan9.ini,
and I am able to boot th
On Mar 30, 5:35 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > 1) I can not resolv any name from my terminal, even though my server's
> > ndb database has declared a subnet with an default dns entry.
>
> Does 'cat /net/ndb' on the terminal show a 'dns=' entry?
>
this is the info cat /net/ndb g
> > 2) I can not authenticate to the server with any user from my terminal
> > system even though I can see the attempted conecction in the fossil
> > console.
>
> Running the auth/debug command on the terminal may reveal a clue.
I ran auth/debug, this is what it tells:
no p9sk1 keys found in fac
On Mar 30, 12:19 pm, 9f...@hamnavoe.com (Richard Miller) wrote:
> >> So, save for the ipwg, everything seems ok. The server akenaton as
>
> > that could be your problem. there's no route out.
>
> > - erik
>
> But that's not relevant when trying to reach machines
> on the same subnet:
>
> > I have
On Mar 30, 9:38 am, quans...@quanstro.net (erik quanstrom) wrote:
> > So, save for the ipwg, everything seems ok. The server akenaton as
>
> that could be your problem. there's no route out.
>
> - erik
I have ipwg delcared in my server's ndb file, but still it does not
show up in cat /netndb in m
>
> I think the real problem is trying to resolve unqualified names without
> a 'dnsdomain' defined -- see ndb(6)
I tried with:
ip/ping akenaton.amarna.net
and yes, it works with a qualified name for the server. So that seems
to be the problem with dns. I then tried the line:
dnsdomain=amarna.n
On Apr 2, 6:58 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > I then tried the line:
>
> > dnsdomain=amarna.net
>
> > in my terminal's ndb file, but it keeps failing with unqualified
> > names.
>
> You need something more like this:
>
> ipnet=localnet ip=10.0.0.0 ipmask=255.255.255.0
>
> there are two ways you can get a short name to work
> - use a sys=xyz entry. if you also want to use dns to
> reach this node it would be conventional to have sys=xyz dom=xyz.dom.
That was the first thing I did. My tipical entry en ndb looks like:
ip=10.0.0.2 ether=jhgsfs7sfs788 sys=akenaton
I have made (thanks to all of you) progress with my configuration.
I thought the only problem to solve was the dns solving short names,
but I am still unable to connect using plan9.
I try:
9fs akenaton /n/akenaton
and get the error:
srv net!akenaton!9fs: mount failed: fossil authCheck: auth pro
On Apr 2, 10:35 am, 9f...@hamnavoe.com (Richard Miller) wrote:
> > See? It seems everything is well configured, but still no short name
> > resolution.
> > What puzzles me more is, the same dnsquery used at the server give
> > identical good results for both the short and large names:
>
> Do you ha
10 matches
Mail list logo
