9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ezequiel Aragon <aragonezequiel@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] my plan9 server isn't responding
Date: Fri, 30 Mar 2012 08:51:38 +0000	[thread overview]
Message-ID: <4cc0def2-7cad-481d-8405-a38ec9394e43@m16g2000yqc.googlegroups.com> (raw)

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 the new system ok. I use ndb/ipquery, ndb/cs and
ndb/dnsquery to test that my server is well configured and all of them
give expected results. Then, I instaled another plan9 system (a
terminal) and told it to use dhcp with ip/ipconfig. I can see the
right ip given to it by the server in /net/ipselftab, but:

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

I have to machines declared in ndb/local, akenaton ip 10.0.0.2 and
nefertiti ip 10.0.0.3, I can't say things like:
9fs akenaton
or
cpu -h akenaton
or even
ip/ping -n 4 akenaton

as the terminal system (nefertiti) don't know the dns.
Is is not supposed dhcp will feed nefertiti not only with an ip but
also dns an auth information?

What is missing in my configuration? Any clues?
If someone needs more information about any of my conf. files, please
tell me.
thanks in advance



             reply	other threads:[~2012-03-30  8:51 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  8:51 Ezequiel Aragon [this message]
2012-03-30  9:35 ` Richard Miller
2012-03-30 13:27 ` Ezequiel Aragon
2012-03-30 13:38   ` erik quanstrom
2012-03-30 16:19     ` Richard Miller
2012-04-02  9:28       ` Ezequiel Aragon
2012-04-02  9:28       ` Ezequiel Aragon
2012-04-02 10:58         ` Richard Miller
2012-04-02 13:15           ` Ezequiel Aragon
     [not found]           ` <75e042ae-ab8a-4655-9a2d-e2a2568eadf3@do6g2000vbb.googlegroups.co>
2012-04-02 13:30             ` erik quanstrom
2012-04-02 14:22         ` Ezequiel Aragon
2012-04-02 14:33           ` erik quanstrom
2012-04-02 14:35           ` Richard Miller
2012-04-03  8:38             ` Ezequiel Aragon
2012-04-03  8:45               ` Charles Forsyth
2012-04-03 10:47               ` Lucio De Re
2012-04-03 12:53                 ` erik quanstrom
2012-04-03 17:24               ` Anthony Sorace
2012-04-04  4:19                 ` Lucio De Re
2012-04-03  8:38         ` Ezequiel Aragon
2012-03-30 13:56   ` Lucio De Re
2012-03-30 14:45     ` Lyndon Nerenberg
2012-03-30 13:30 ` Ezequiel Aragon
2012-03-30 16:09   ` Richard Miller
2012-04-02  9:27 ` Ezequiel Aragon
2012-04-02  9:44   ` Richard Miller
2012-04-02  9:55     ` Lucio De Re
2012-04-02 11:04       ` Richard Miller

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=4cc0def2-7cad-481d-8405-a38ec9394e43@m16g2000yqc.googlegroups.com \
    --to=aragonezequiel@gmail.com \
    --cc=9fans@9fans.net \
    /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).