9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] non-9front dhcp server -> /lib/ndb/local ignored?
Date: Tue, 29 Dec 2015 02:31:25 +0000	[thread overview]
Message-ID: <147B6551-279A-41AE-80EA-E475B26CA782@quintile.net> (raw)
In-Reply-To: <c0a7642344fbb691d422a28d549b7633@cb.inri.net>

maybe being foolish, but from memory - the config you see does not include a dnsdomain= entry so dns(1) does not know which names are local and which are not.

in you example you use ping, does that work with a fully qualified domain name?

-Steve


On 29 Dec 2015, at 01:09, sl@stanleylieber.com wrote:

>> I have cpu server and auth server which I want to use from both home and internet.
>> those names are:
>> (1) hebe (or hebe.local) in home and hebe.nyx.link from internet
>> (2) grid (or grid.local) in home and grid.nyx.link form internet
>> 
>> I have plan9 terminal on virtualbox on macbook.
>> that is, I use the terminal in two types of environment.
>> (a) local wifi in my home with plan9 based DHCP and DNS.
>> (b) mobile router wifi with mobile ISP based DHCP and DNS.
>> 
>> of course we need fqdn in accessing from internet.
> 
> My setup is similar but slightly different.
> 
> In my (b) environment, I boot the 9front.iso livecd off of an image on
> a USB stick and then bind my customizations (including /lib/ndb/local)
> over the running system before launching my network configuration. My
> 9front terminal then gets an IP address from the free wifi access point
> here in the building. I don't have any control over which address or what
> settings my 9front terminal receives from that DHCP server. Once I've
> received my DHCP lease my terminal *can* resolve values from ndb but
> *cannot* operate on them:
> 
>    ; ndb/query sys mars2
>    sys=mars2 dom=mars2.inri.net ether=525400099935 ip=216.126.196.35 ipmask=255.255.255.224 ipgw=216.126.196.33 auth=mars2.inri.net authdom=mars2 dns=208.67.222.222 dns=208.67.220.220 mx=mars2.inri.net pref=5 txtrr=v=spf1 mx -all 
>    ; ip/ping -n 3 mars2
>    ip/ping: couldn't dial icmp!mars2!1: cs: can't translate address: dns: resource does not exist; negrcode
>    ;
> 
> Similarly, auth= authdom= entries in /lib/ndb/local are ignored, but
> work fine when I add them manually to /net/ndb.
> 
> I'd point out again that my terminal here at work is using the exact
> same /lib/ndb/local file as my machines at home, all of which can
> successfully perform the ip/ping -n 3 mars2 operation, and recognize
> auth servers, without needing to edit /net/ndb manually.
> 
> Maybe I'm just doing something wrong, but the only real difference
> I am aware of is that all of my machines at home are completely
> controlled by Plan 9, while my terminal here at work gets its IP
> address from a non-Plan 9 DHCP server.
> 
> 
>>    ns=hebe.loca
> 
> Is this a typo?
> 
> About your setup:
> 
> Doesn't your virtualbox terminal always see itself as being on its own
> local network? Correct me if I'm wrong, but if I understand you correctly,
> your host OS gets its IP from the "mobile router wifi with mobile ISP based
> DHCP and DNS," while your virtualbox terminal gets its IP from virtualbox
> itself. Is your virtualbox terminal getting its IP from virtualbox via
> DHCP, or is it configured in ndb with a static IP address?
> 
> sl


  reply	other threads:[~2015-12-29  2:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  1:09 sl
2015-12-29  2:31 ` Steve Simon [this message]
2015-12-29  3:56 ` arisawa
2015-12-29  5:04 ` cinap_lenrek
  -- strict thread matches above, loose matches on Subject: below --
2015-12-29 19:14 sl
2016-01-04 17:47 ` Ethan Grammatikidis
2015-12-29  2:55 sl
2015-12-28 20:34 sl
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=147B6551-279A-41AE-80EA-E475B26CA782@quintile.net \
    --to=steve@quintile.net \
    --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).