9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ndb/csquery: what is dns is not up?
Date: Wed, 23 Apr 2003 08:59:48 -0400	[thread overview]
Message-ID: <0d7357fe22689e4f5ae741260582305f@plan9.bell-labs.com> (raw)
In-Reply-To: <20030423145118.J19261@cackle.proxima.alt.za>

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Because ipquery starts and an ipaddress and looks through the database looking
for attributes bound to that address, then to the subnet containing that address,
then the subnet containing that subnet, ad nauseam looking for the attributes.

There is no ip address corresponding to an authdom, like outside.plan9.bell-labs.com.

I'll answer about sshnet as soon as I look at a man page to see what it
is.

[-- Attachment #2: Type: message/rfc822, Size: 2982 bytes --]

From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ndb/csquery: what is dns is not up?
Date: Wed, 23 Apr 2003 14:51:18 +0200
Message-ID: <20030423145118.J19261@cackle.proxima.alt.za>

On Wed, Apr 23, 2003 at 08:22:59AM -0400, David Presotto wrote:
>
> ndb/csquery
> > p9
>
> [ ... ]

Why does
	ndb/query authdom outside.plan9.bell-labs.com auth
return
	sources.cs.bell-labs.com

whereas
	ndb/ipquery authdom outside.plan9.bell-labs.com auth

returns no response?

I'm trying to get replica/pull to work across sshnet, but for some
reason the authentication server is not being discovered whereas it
seems that the 9fs connection is established correctly.

I managed to get /net/dns to install itself once, but the rest of the
time I have only net/ip and net/tcp and therefore not much in the line
of useful information to reach the remote services :-)

Not that I understand all the complications, I'm sure there's a lot
that would be obvious to someone more comfortable with Plan 9
networking.

++L

PS: Starting a new factotum seems to reroute the auth requests via the
ssh tunnel rather than attempt to go via the original default route
and that isn't what I expect either.

  reply	other threads:[~2003-04-23 12:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-23  4:37 ron minnich
2003-04-23  8:09 ` Charles Forsyth
2003-04-23 12:22 ` David Presotto
2003-04-23 12:51   ` Lucio De Re
2003-04-23 12:59     ` David Presotto [this message]
2003-04-23 13:16       ` Lucio De Re
2003-04-23 13:20         ` David Presotto
2003-04-23 13:34           ` Lucio De Re
2003-04-23 13:21         ` David Presotto
2003-04-23 14:58           ` Russ Cox
2003-04-23 21:57             ` Geoff Collyer
2003-04-24 12:16               ` Russ Cox
2003-04-23 13:25         ` Lucio De Re
2003-04-23 13:17     ` David Presotto
2003-04-23 13:29       ` Lucio De Re

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=0d7357fe22689e4f5ae741260582305f@plan9.bell-labs.com \
    --to=presotto@closedmind.org \
    --cc=9fans@cse.psu.edu \
    /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).