From owner-freebsd-hackers Thu Apr 17 18:14:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA21664 for hackers-outgoing; Thu, 17 Apr 1997 18:14:49 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21659 for ; Thu, 17 Apr 1997 18:14:44 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost.lan.awfulhak.org [127.0.0.1]) by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id BAA02886; Fri, 18 Apr 1997 01:49:30 +0100 (BST) Message-Id: <199704180049.BAA02886@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: johnp@lodgenet.com cc: freebsd-hackers@freebsd.org Subject: Re: rsh and ppp In-reply-to: Your message of "Wed, 16 Apr 1997 22:34:28 CDT." <199704170334.WAA00383@knight.trosoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Apr 1997 01:49:29 +0100 From: Brian Somers Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 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.. > Help??? > John Prince The problem is that RPC based programs expect the client side to come from a specific port. The alias software changes that port, breaking the protocol. There's now a "keep the port the same if you can" option in the alias code, but it's not in ppp yet - just natd (ports/net/natd). -- Brian , Don't _EVER_ lose your sense of humour....