From: sl@stanleylieber.com
To: 9front@9front.org
Subject: non-9front dhcp server -> /lib/ndb/local ignored?
Date: Mon, 28 Dec 2015 15:34:59 -0500 [thread overview]
Message-ID: <3054d91ebbb74cc775f990e0a4a93ac6@cb.inri.net> (raw)
At my job we have a free wifi access point that I connect
to from 9front like this:
; ip/ipconfig # NOTE: DHCP server is not Plan 9.
This gets me on the Internet. Everything works.
Except, values configured in /lib/ndb/local all seem to
be ignored. No sys= or auth= entries are recognized. In
order to successfully cpu/import remote Plan 9 machines,
I have to manually add auth= authdom= entries for the
corresponding auth servers in /net/ndb, and then refer
to them by the FQDNs.
At home, I use an identical /lib/ndb/local. All home
machines either PXE or TCP boot from the same file
server where the ndb file is stored. All of these
machines can successfully refer to local sys= entries,
even those that are in separate ipnets.
From all of this, it seems like Plan 9 machines that get
DHCP from a non-Plan 9 machine ignore /lib/ndb/local.
What's going on?
sl
next reply other threads:[~2015-12-28 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 20:34 sl [this message]
2015-12-29 0:20 ` [9front] " arisawa
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=3054d91ebbb74cc775f990e0a4a93ac6@cb.inri.net \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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).