* [9fans] dns question
@ 2007-11-19 23:23 ron minnich
2007-11-20 0:59 ` Russ Cox
2007-11-20 3:46 ` lucio
0 siblings, 2 replies; 9+ messages in thread
From: ron minnich @ 2007-11-19 23:23 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
I am trying to get THNX ready for IWP9 and I have a problem I don't
understand. Almost everything works on the net save dns. In fact I am
drawterm'ed into it across the net from another box, that's how I got
the text from below.
I am bringing up the Plan 9 guest and it is succeeding at DHCP. The
router/dns/DHCP box is at 192.168.18.10.
Here is my iproute
cpu% cat /net/iproute
0.0.0.0 /96 192.168.18.10 4 none -
192.168.18.0 /120 192.168.18.0 4i ifc 1
192.168.18.0 /128 192.168.18.0 4b ifc -
192.168.18.190 /128 192.168.18.190 4u ifc 1
192.168.18.255 /128 192.168.18.255 4b ifc -
127.0.0.0 /128 127.0.0.0 4b ifc -
127.0.0.1 /128 127.0.0.1 4ip ifc 0
127.255.255.255 /128 127.255.255.255 4b ifc -
255.255.255.255 /128 255.255.255.255 4b ifc 1
cpu%
and /net/ndb:
cpu% cat /net/ndb
ip=192.168.18.190 ipmask=255.255.255.0 ipgw=192.168.18.10
dns=192.168.18.10
dns=146.246.250.1
cpu%
BUT: /lib/ndb/local is this:
ipnet=lguestnet ip=192.168.19.0 netmask=255.255.255.0 ipgw=192.168.19.1
proto=tcp cpu=lguest fs=lguest auth=lguest authdom=lguestdom
dns=192.168.19.1
sys=lguest ip=192.168.19.2 dom=lguest authdom=lguest auth=lguest
The problem: no DNS. Snooping from the linux and plan 9 side shows no
packets go to 192.168.18.10 for dns requests. Is the /lib/ndb/local
misdirecting dns somehow? I hate to yank the /lib/ndb/local, however,
as it is useful when the plan 9 guest is running in NAT as opposed to
BRIDGE mode.
The cpurc is this:
ip/ipconfig ether /net/ether0
date > /env/boottime
# replace FILESERVER with the name of your file server
# here we start with kfs, your local disk file system
fileserver=kfs
# replace FACEDOM with the local domain to be used in the faces database
facedom=FACEDOM
# mount points
mntgen -s slashn && chmod 666 /srv/slashn
# name translation, cs sets /dev/sysname
ndb/cs
sysname=`{cat /dev/sysname}
ndb/dns -r
and the sysname is this:
cpu% cat /dev/sysname
192.168.18.190cpu%
I am not sure I see what's up. I can't run acid on this (one of the
issues with the lguest port still :-)
dnsdebug just sits there and appears to time out.
any help greatly appreciated.
thanks
ron
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-19 23:23 [9fans] dns question ron minnich
@ 2007-11-20 0:59 ` Russ Cox
2007-11-20 20:47 ` ron minnich
2007-11-20 3:46 ` lucio
1 sibling, 1 reply; 9+ messages in thread
From: Russ Cox @ 2007-11-20 0:59 UTC (permalink / raw)
To: 9fans
> The problem: no DNS. Snooping from the linux and plan 9 side shows no
> packets go to 192.168.18.10 for dns requests. Is the /lib/ndb/local
> misdirecting dns somehow? I hate to yank the /lib/ndb/local, however,
> as it is useful when the plan 9 guest is running in NAT as opposed to
> BRIDGE mode.
echo debug >/net/dns
and then try to resolve some new name
and look at /sys/log/dns
russ
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-19 23:23 [9fans] dns question ron minnich
2007-11-20 0:59 ` Russ Cox
@ 2007-11-20 3:46 ` lucio
1 sibling, 0 replies; 9+ messages in thread
From: lucio @ 2007-11-20 3:46 UTC (permalink / raw)
To: 9fans
> I hate to yank the /lib/ndb/local, however,
> as it is useful when the plan 9 guest is running in NAT as opposed to
> BRIDGE mode.
Isn't that the purpose of specifying a a different NDB on the command line?
++L
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 0:59 ` Russ Cox
@ 2007-11-20 20:47 ` ron minnich
2007-11-20 20:54 ` ron minnich
2007-11-20 21:39 ` Richard Miller
0 siblings, 2 replies; 9+ messages in thread
From: ron minnich @ 2007-11-20 20:47 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
Here is what I have.
192.168.18.190 Nov 20 13:36:39 starting dns on 192.168.18.190
192.168.18.190 Nov 20 17:54:06 Rwrite tag 2 count 6 11
192.168.18.190 Nov 20 17:54:06 Tclunk tag 2 fid 262
192.168.18.190 Nov 20 17:54:06 Rclunk tag 2 7
192.168.18.190 Nov 20 17:54:18 Twalk tag 9 fid 137 newfid 264 nwname 1
0:ndb.database
192.168.18.190 Nov 20 17:54:18 Rerror tag 9 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:20 [151] dnresolve1 cnn.com 1 1
192.168.18.190 Nov 20 17:54:21 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:21 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:21 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:21 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:21 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:21 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:22 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:22 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:22 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:22 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:22 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:22 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:23 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:23 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:23 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:23 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:23 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:23 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:23 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:23 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:23 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:23 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 264 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 [151] dnresolve1 cnn.com 5 1
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:24 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:24 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.sys
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 Twalk tag 2 fid 137 newfid 266 nwname 1
0:ndb.dom
192.168.18.190 Nov 20 17:54:25 Rerror tag 2 ename dns: file does not exist 33
192.168.18.190 Nov 20 17:54:25 rereading /net/ndb
192.168.18.190 Nov 20 17:54:25 rereading /lib/ndb/local
192.168.18.190 Nov 20 17:54:25 rereading /lib/ndb/common
192.168.18.190 Nov 20 17:55:28 Tauth tag 9 afid 295 uname bootes aname
192.168.18.190 Nov 20 17:55:28 Rerror tag 9 ename dns: dns:
authentication not required 46
192.168.18.190 Nov 20 17:55:28 Tattach tag 9 fid 295 afid -1 uname bootes aname
192.168.18.190 Nov 20 17:55:28 Rattach tag 9 qid (0000000000000000 60 d) 20
192.168.18.190 Nov 20 17:55:40 Twalk tag 1 fid 259 newfid 334 nwname 1 0:dns
192.168.18.190 Nov 20 17:55:40 Rwalk tag 1 nwqid 1 0:(0000000000000001 61 ) 22
192.168.18.190 Nov 20 17:55:40 Topen tag 1 fid 334 mode 2
192.168.18.190 Nov 20 17:55:40 Ropen tag 1 qid (0000000000000001 61 )
iounit 0 24
192.168.18.190 Nov 20 17:55:40 Twrite tag 1 fid 334 offset 0 count 9 '!$auth ip'
192.168.18.190 Nov 20 17:55:41 Rerror tag 1 ename dns: resource does
not exist 37
192.168.18.190 Nov 20 17:55:41 Tclunk tag 1 fid 334
192.168.18.190 Nov 20 17:55:41 Rclunk tag 1 7
I just realized I know less about dns than I thought :-)
ron
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 20:47 ` ron minnich
@ 2007-11-20 20:54 ` ron minnich
2007-11-20 21:39 ` Richard Miller
1 sibling, 0 replies; 9+ messages in thread
From: ron minnich @ 2007-11-20 20:54 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
Hmm, could this be a race condition? If I start dns some time after
boot, it works. And it seems to take a long time for ipconfig to get
its IP and set things up. I am not sure what's up here.
ron
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 20:47 ` ron minnich
2007-11-20 20:54 ` ron minnich
@ 2007-11-20 21:39 ` Richard Miller
2007-11-20 21:44 ` ron minnich
1 sibling, 1 reply; 9+ messages in thread
From: Richard Miller @ 2007-11-20 21:39 UTC (permalink / raw)
To: 9fans
> 192.168.18.190 Nov 20 13:36:39 starting dns on 192.168.18.190
Looks like you are running an oldish version of dns. Current version
started with 'dns -r' should give you a log message something like
starting dns resolver on 192.168.18.190's /net
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 21:39 ` Richard Miller
@ 2007-11-20 21:44 ` ron minnich
2007-11-20 22:28 ` Richard Miller
0 siblings, 1 reply; 9+ messages in thread
From: ron minnich @ 2007-11-20 21:44 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
This close to IWP9 I'm reluctant to do a pull on THNX. What to do?
ron
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 21:44 ` ron minnich
@ 2007-11-20 22:28 ` Richard Miller
2007-11-21 18:23 ` ron minnich
0 siblings, 1 reply; 9+ messages in thread
From: Richard Miller @ 2007-11-20 22:28 UTC (permalink / raw)
To: 9fans
> This close to IWP9 I'm reluctant to do a pull on THNX. What to do?
I'd try copying just /n/sources/plan9/386/bin/ndb/dns to /386/bin/ndb
(save your current one first of course). When it starts, you should
see a log message indicating that it's found a server to send recursive
queries too - something like
added local dns server local#dns#server0 at 192.168.xx.yy
If it's not getting a server from dhcp via /net/ndb, you can brute-force
one in plan9.ini by setting
DNSSERVER=192.168.xx.yy
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [9fans] dns question
2007-11-20 22:28 ` Richard Miller
@ 2007-11-21 18:23 ` ron minnich
0 siblings, 0 replies; 9+ messages in thread
From: ron minnich @ 2007-11-21 18:23 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
On Nov 20, 2007 2:28 PM, Richard Miller <9fans@hamnavoe.com> wrote:
> > This close to IWP9 I'm reluctant to do a pull on THNX. What to do?
>
> I'd try copying just /n/sources/plan9/386/bin/ndb/dns to /386/bin/ndb
> (save your current one first of course).
that did the trick. I'm surprised but happy.
I'm also installing inferno on THNX, I figure people might want it.
ron
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2007-11-21 18:23 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-11-19 23:23 [9fans] dns question ron minnich
2007-11-20 0:59 ` Russ Cox
2007-11-20 20:47 ` ron minnich
2007-11-20 20:54 ` ron minnich
2007-11-20 21:39 ` Richard Miller
2007-11-20 21:44 ` ron minnich
2007-11-20 22:28 ` Richard Miller
2007-11-21 18:23 ` ron minnich
2007-11-20 3:46 ` lucio
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).