> This is unusual, at the least. Typically, you have something like:
>
> authdom=mydomain.com auth=whatever.mydomain.com
>
> in its own stanza.
It works for me where I have a few different sites with distinct auth
servers and, to be safe, auth domains. And though this may be just
luck, it follo
On Apr 3, 2012, at 4:38 , Ezequiel Aragon wrote:
> ipnet=mynet ip=10.0.0.0 ipmask=255.255.255.0
>ipgw=10.0.0.1
>dns=10.0.0.2
>dnsdomain=amarna.net
>auth=akenaton.amarna.net authdomain=amarna.net
>cpu=akenaton.amarna.net
>fs=akenaton.amarna.net
This is unusual, at the leas
> "authdom" not "authdomain". Not a very forgiving database format.
/n/sources/contrib/quanstro/root/sys/src/cmd/ndb/vrfy.y
/n/sources/contrib/quanstro/root/sys/man/10/ndbvrfy
this program might be a useful bit in sorting out your ndb file.
- erik
> auth=akenaton.amarna.net authdomain=amarna.net
"authdom" not "authdomain". Not a very forgiving database format.
++L
/net/ndb is for the bootstrap data returned by (say) DHCP, enough to find
/lib/ndb and other resources and get going. it isn't a cache for ndb data.
On 3 April 2012 09:38, Ezequiel Aragon wrote:
> Why isn't dnsdomain fetched with the rest of the info to the terminal?
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
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
> 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 have in /lib/ndb/local on the terminal as I suggested:
ipnet=localnet ip=10
On Mon Apr 2 10:31:33 EDT 2012, aragonezequ...@gmail.com wrote:
>
> > 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 ti
> 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 think I have isolated the problem.
> I configured my server ndb file with auth and fs using the server
> fully qualified name.
> As a result, now, my terminal ndb info looks more promising:
>
> cat /net/ndb
> sys=nefertiti
> dom=nefertiti.amarna.net
> fs=10.0.0.2
> auth=10.0.0.2
> dn
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
>
> ... and is it really necessary for the terminal to have its own ndb
> file? At best, it's redundant, at worst, conflicting.
Simplest practice is for the terminal to get its root file system from
the server, so they are sharing /lib/ndb/local. If the terminal has
its own root, it needs its own
> 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
dnsdomain=amarna.net
> By the way, I am trying to connect as ezequiel with
>> I have ipwg delcared in my server's ndb file
>
> s/ipwg/ipgw/
>
> Is it spelled correctly in server's /lib/ndb/local?
... and is it really necessary for the terminal to have its own ndb
file? At best, it's redundant, at worst, conflicting.
++L
> I have ipwg delcared in my server's ndb file
s/ipwg/ipgw/
Is it spelled correctly in server's /lib/ndb/local?
>
> 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 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
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
>> 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 to machines declared in ndb/local, akenaton ip 10.0.0.2 and
> nefertiti ip 1
> no p9sk1 keys found in factotum
So, put one in and try again.
auth/factotum -g 'proto=p9sk1 user= dom= !password?'
where and are your username and authdom
On 2012-03-30, at 6:56 AM, Lucio De Re wrote:
> I had to use an IP number in the ipgw pair in the ipnet to force it to appear
> in /net/ndb. I'm not sure whether this is expected but undocumented
> bahaviour or a bug, but a domain name didn't cut it. I'd be curious to know.
A hostname can ma
> So, save for the ipwg, everything seems ok. The server akenaton as
> ip=10.0.0.2 and it's ndb database has declared all these services.
> Why then, isn't dns working?
I had to use an IP number in the ipgw pair in the ipnet to force it to appear
in /net/ndb. I'm not sure whether this is expecte
> > 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
> So, save for the ipwg, everything seems ok. The server akenaton as
that could be your problem. there's no route out.
- erik
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
> 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?
> 2) I can not authenticate to the server with any user from my terminal
> system even though I can see
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
28 matches
Mail list logo
