From owner-freebsd-hackers  Wed Apr 16 21:23:29 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA06269
          for hackers-outgoing; Wed, 16 Apr 1997 21:23:29 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA06263
          for <freebsd-hackers@freebsd.org>; Wed, 16 Apr 1997 21:23:23 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id OAA08661; Thu, 17 Apr 1997 14:23:09 +1000 (EST)
Date: Thu, 17 Apr 1997 14:23:08 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: John Prince <johnp@lodgenet.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: rsh and ppp
In-Reply-To: <199704170334.WAA00383@knight.trosoft.com>
Message-ID: <Pine.BSF.3.91.970417142056.10264K-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Wed, 16 Apr 1997, John Prince wrote:

> Why does the rsh command not work when alias is enabled with ppp?
> I get the error ...
> "select: protocol failure in circuit setup" 
> This happens only on ppp connections. On the local net rsh works fine.
> Release 2.2.1-RELEASE..

Sounds like an rsh emulation is not built into the NAT/alias code.  rsh 
sets up a separate connection for stderr, which is established from 
server to client.  Since you are running with a NAT, the server can't set 
up the extra connection to the client.  If you can, run sshd on the 
server and use ssh in place of rsh.  ssh only uses a single stream.

Danny