From: arisawa@ar.aichi-u.ac.jp arisawa@ar.aichi-u.ac.jp
Subject: [9fans] nfs server
Date: Mon, 12 Apr 1999 05:03:45 -0400 [thread overview]
Message-ID: <19990412090345.2xzN5C5RTR5XcPAuqgMA8SFll71XMj6LrYXO5wAeRR0@z> (raw)
Hello 9fans.
I added UNIX to my network and added the name to:
/lib/ndb/nfs
/lib/ndb/local
to enable access to my Plan9 file system.
However nfs server rejected to connect with the message:
auth: unknown ip address: host=202.250.160.73
The message comes from:
if(getdnsdom(cmd->host, dom, sizeof(dom))<0){
clog("auth: unknown ip address: host=%s", cmd->host);
return error(reply, 1);
}
in nfsmount.c.
I experienced this message some months (or a year) ago when I did something.
getdnsdom is defined rpcserver.c; the function gets domname from IP using
sprint(buf, "echo %d.%d.%d.%d ptr | ndb/dnsquery",
ip>>24, (ip>>16)&0xff, (ip>>8)&0xff, ip&0xff);
On the other hands, manual says:
Ndb/dnsquery can be used to query ndb/dns to see how it
resolves requests. Ndb/dnsquery prompts for commands of the
form
domain-name request-type
where request-type can be ip, mx, ns, cname, ptr.... In the
It seems to me dnsquery is used to get IP from domname.
So I made some experiments whether dnsquery can really answer domname
from IP or not:
echo 202.250.160.73 ptr | ndb/dnsquery
This is an example. I tried several IPs and found that some IPs are successfully
processed but some are not.
We have ndb/query that gets domname from IP,
and rpcserver.c already has a similar function:
getdom(ulong ip, uchar *name, int len)
It is strange that getdom is not used anywhere.
I replaced getdnsdom by getdom in nfsmount.c and after that my UNIX can be
authenticated by Plan9.
There may be a reason that getdom should not be used.
Comments are welcome.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~1999-04-12 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-12 9:03 arisawa [this message]
1999-04-12 13:17 presotto
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=19990412090345.2xzN5C5RTR5XcPAuqgMA8SFll71XMj6LrYXO5wAeRR0@z \
--to=arisawa@ar.aichi-u.ac.jp \
/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).