From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: David Presotto To: 9fans@cse.psu.edu Subject: Re: [9fans] ndb/csquery: what is dns is not up? In-Reply-To: <20030423151624.M19261@cackle.proxima.alt.za> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-lijlsqaapntvadcmwvybeibbee" Date: Wed, 23 Apr 2003 09:21:34 -0400 Topicbox-Message-UUID: 96b9d3f8-eacb-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-lijlsqaapntvadcmwvybeibbee Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit God that message was terrible. I meant to say: 1) have sshnet support a /net/ndb and set it up the usual way. 2) have sshnet's simulated cs, first search /net/ndb when resolving queries. That would make it a lot more useful. --upas-lijlsqaapntvadcmwvybeibbee Content-Type: message/rfc822 Content-Disposition: inline Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Wed Apr 23 09:17:21 EDT 2003 Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Wed Apr 23 09:17:19 EDT 2003 Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id ED88F199BE; Wed, 23 Apr 2003 09:17:09 -0400 (EDT) Delivered-To: 9fans@cse.psu.edu Received: from cackle.proxima.alt.za (cackle.proxima.alt.za [196.30.44.141]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 2092219988 for <9fans@cse.psu.edu>; Wed, 23 Apr 2003 09:16:34 -0400 (EDT) Received: from cackle.proxima.alt.za (localhost [127.0.0.1]) by cackle.proxima.alt.za (8.12.9/8.12.3) with ESMTP id h3NDGTNF020193 for <9fans@cse.psu.edu>; Wed, 23 Apr 2003 15:16:32 +0200 (SAST) Received: (from lucio@localhost) by cackle.proxima.alt.za (8.12.9/8.12.3/Submit) id h3NDGSxV020192 for 9fans@cse.psu.edu; Wed, 23 Apr 2003 15:16:28 +0200 (SAST) From: Lucio De Re To: 9fans@cse.psu.edu Subject: Re: [9fans] ndb/csquery: what is dns is not up? Message-ID: <20030423151624.M19261@cackle.proxima.alt.za> Mail-Followup-To: 9fans@cse.psu.edu References: <20030423145118.J19261@cackle.proxima.alt.za> <0d7357fe22689e4f5ae741260582305f@plan9.bell-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <0d7357fe22689e4f5ae741260582305f@plan9.bell-labs.com>; from David Presotto on Wed, Apr 23, 2003 at 08:59:48AM -0400 Organization: Proxima Research & Development Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.11 Precedence: bulk Reply-To: 9fans@cse.psu.edu X-Reply-To: lucio@proxima.alt.za List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Wed, 23 Apr 2003 15:16:25 +0200 On Wed, Apr 23, 2003 at 08:59:48AM -0400, David Presotto wrote: > > 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. > Oh, OK! I guess the name says it all, once you know what to look for. > I'll answer about sshnet as soon as I look at a man page to see what it > is. Let me be less cryptic, while I have a chance. My office is linked to the Internet via a convoluted path of private networks, with a remote host that I can connect to using SSH. I establish a "tunnel" to that host quite happily using sshnet, which installs a stripped copy of /net. The command srv sources.cs.bell-labs.com sources /n/sources returns the reassuring "post..." and, in the absence of a factotum key, prompts me for the proxima/......... which I use to authenticate. Sadly, it seems to me that factotum attempts to connect directly to sources.cs.bell-labs.com, according to tcpdump run on the remote host. The diagnostic output from factotum indicates the expected timeout caused by the various filters in the path. If I spawn a new factotum (it really needs an option to be removable, by the way), I believe it fails to identify/resolve the auth server associated with the auth domain. I have no idea quite how to take care of that problem. Ideally, I'd create a /net/ndb entry, but that's not possible with sshnet serving /net. ++L --upas-lijlsqaapntvadcmwvybeibbee--