From owner-freebsd-net@FreeBSD.ORG Sat May 10 10:48:37 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F27037B401; Sat, 10 May 2003 10:48:37 -0700 (PDT) Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA2D943FE1; Sat, 10 May 2003 10:48:36 -0700 (PDT) (envelope-from tinguely@web.cs.ndsu.nodak.edu) Received: from web.cs.ndsu.nodak.edu (localhost [127.0.0.1]) by web.cs.ndsu.nodak.edu (8.12.9/8.11.4) with ESMTP id h4AHmZWr031719; Sat, 10 May 2003 12:48:35 -0500 (CDT) (envelope-from tinguely@web.cs.ndsu.nodak.edu) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.12.9/8.12.8/Submit) id h4AHmZY5031718; Sat, 10 May 2003 12:48:35 -0500 (CDT) (envelope-from tinguely) Date: Sat, 10 May 2003 12:48:35 -0500 (CDT) From: mark tinguely Message-Id: <200305101748.h4AHmZY5031718@web.cs.ndsu.nodak.edu> To: hsu@FreeBSD.org, silby@silby.com, tinguely@web.cs.ndsu.nodak.edu In-Reply-To: <0HEO00C7TLEPTC@mta5.snfc21.pbi.net> cc: freebsd-net@FreeBSD.org cc: freebsd-questions@FreeBSD.org cc: Lars.Koeller@uni-bielefeld.de Subject: Re: Please, Urgent: Need ideas/help to solve PR bin/51586 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 17:48:37 -0000 > This has all the signs of a bug in rsh or one of the libraries it > uses. I asked Lars to try it with ssh instead and he reports that > it works with ssh. We should probably concentrate our search on rsh > code. ssh will not create second connection, nor will the local port be a restricted port (especially port 623). We can see the vscan1 host make an attempt to respond to the remote machine using local port 623 but that packet does not make it to the other machine. Either something happens to that packet after it goes through the BPF (ie, the interface transmission part of the device driver), or somewhere in the network. That is why I suggest another host on the same network as one of the other machines or a protocol analyzer on the network to see if that packet make it through the network. W. Richard Steven has sample networking programs that can be used if he does not want to write one (sock from TCP Illustrated Vol 1 comes to mind http://www.kohala.com/start/unpv12e/unpv12e.tar.gz). --Mark Tinguely