From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <7d57bd30-6e43-4d54-8670-ef6c71fefae1@i5g2000vbk.googlegroups.com> References: <30b7dc5f967768a728276851ef507605@hamnavoe.com> <7d57bd30-6e43-4d54-8670-ef6c71fefae1@i5g2000vbk.googlegroups.com> Date: Wed, 3 Apr 2013 12:54:45 +0200 Message-ID: From: =?UTF-8?B?QmVuY2UgRsOhYmnDoW4=?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bd75cee9c8a2e04d972ae79 Subject: Re: [9fans] [9pi] standardize \ normalize setting dns in Topicbox-Message-UUID: 3d162aa6-ead8-11e9-9d60-3106f5b1d025 --047d7bd75cee9c8a2e04d972ae79 Content-Type: text/plain; charset=UTF-8 what does ndb/query sys $sysname say? try to add ether and dom like this: ip=10.0.0.13 sys=9pi ether=xxxxx... dom=9pi.Home 2013/4/3 > On Mar 28, 8:41 am, 9f...@hamnavoe.com (Richard Miller) wrote: > > For a machine not receiving net configuration via DHCP, the normal > > place to define dns= would be in /lib/ndb/local - 'man 6 ndb' for > > information. > > Yes. I've already figured out that much: > > term% cat /lib/ndb/local > > database= > file=/lib/ndb/local > file=/lib/ndb/common > > auth=sources.cd.bell-labs.com authdom=outside.plan9.bell-labs.com > > ip=127.0.0.1 sys=localhost dom=localhost > > ipnet=Home ip=10.0.0.0 ipmask=255.255.255.0 > ipgw=10.0.0.138 > dns=1.2.3.4 # (my isp's dns) > dns=8.8.8.8 # (googleA) > dns=8.8.4.4 # (googleB) > dns=10.0.0.138 # (my router for when the net is down but I still > want > local quarries getting through and local dom - .Home - requests) > auth=9pi > cpu=9pi > > ip=10.0.0.13 sys=9pi > > The thing is, the way I understand and implement it, you have your > basic networking split in at least two places: The /lib/ndb/local file > and the ip/ipconfig command arguments (being called from > termrc.local...). Now, if there's a DHCP then you can forgo /lib/ndb/ > local and just specify an empty "ipconfig=". However, on a static ip > you're only allowed to do everything except feeding it a dns. > > My idea is to have a line or two added to termrc.local that will parse > a single dns var from the cmdline.txt file. This way you can get the > same convenience you'd get with DHCP in a static setup. > > I'm not sure it's a possible needless un +\-foreseen complication, > lack of interest, an oversight, a security concern or whatever... But > it seems to me that it could simplify things a little. > > Just a thought really. > > p.s. This is my third or fourth attempt at a reply. The first two were > on the new groups interface. This attempt is on the old one. hopefully > those aren't coming out somewhere as double\triple\quadruple posts... > > --047d7bd75cee9c8a2e04d972ae79 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
what does ndb/query sys $sysname say?

try to add ether and dom like this:

ip=3D10.0= .0.13 sys=3D9pi ether=3Dxxxxx... dom=3D9pi.Home



2013/4/3 <c117152@rmqkr.net>
On Mar 28, 8:41=C2=A0am, 9f...@hamnavoe.com (Richard Miller) wrote:<= br> > For a machine not receiving net configuration via DHCP, the normal
> place to define dns=3D would be in /lib/ndb/local - 'man 6 ndb'= ; for
> information.

Yes. I've already figured out that m= uch:

term% cat /lib/ndb/local

database=3D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 file=3D/lib/ndb/local
=C2=A0 =C2=A0 =C2=A0 =C2=A0 file=3D/lib/ndb/common

auth=3Dsource= s.cd.bell-labs.com authdom=3Doutside.plan9.bell-labs.com

ip=3D127.0.0.1 sys=3Dlocalhost dom=3Dlocalhost

ipnet=3DHome ip=3D10.0.0.0 ipmask=3D255.255.255.0
=C2=A0 =C2=A0 =C2=A0 =C2=A0 ipgw=3D10.0.0.138
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dns=3D1.2.3.4 # (my isp's dns)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dns=3D8.8.8.8 # (googleA)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dns=3D8.8.4.4 # (googleB)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dns=3D10.0.0.138 # (my router for when the net = is down but I still want
local quarries getting through and local dom - .Home - requests)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 auth=3D9pi
=C2=A0 =C2=A0 =C2=A0 =C2=A0 cpu=3D9pi

ip=3D10.0.0.13 sys=3D9pi

The thing is, the way I understand and implement it, you have your
basic networking split in at least two places: The /lib/ndb/local file
and the ip/ipconfig command arguments (being called from
termrc.local...). Now, if there's a DHCP then you can forgo /lib/ndb/ local and just specify an empty "ipconfig=3D". However, on a stat= ic ip
you're only allowed to do everything except feeding it a dns.

My idea is to have a line or two added to termrc.local that will parse
a single dns var from the cmdline.txt file. This way you can get the
same convenience you'd get with DHCP in a static setup.

I'm not sure it's a possible needless un +\-foreseen complication,<= br> lack of interest, an oversight, a security concern or whatever... But
it seems to me that it could simplify things a little.

Just a thought really.

p.s. This is my third or fourth attempt at a reply. The first t= wo were
on the new groups interface. This attempt is on the old one. hopefully
those aren't coming out somewhere as double\triple\quadruple posts...

--047d7bd75cee9c8a2e04d972ae79--