From owner-freebsd-questions@FreeBSD.ORG Fri May 9 07:24:15 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6716537B401; Fri, 9 May 2003 07:24:15 -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 86AB443FBD; Fri, 9 May 2003 07:24:14 -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 h49EODWr022226; Fri, 9 May 2003 09:24:13 -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 h49EOCVe022225; Fri, 9 May 2003 09:24:12 -0500 (CDT) (envelope-from tinguely) Date: Fri, 9 May 2003 09:24:12 -0500 (CDT) From: mark tinguely Message-Id: <200305091424.h49EOCVe022225@web.cs.ndsu.nodak.edu> To: Lars.Koeller@uni-bielefeld.de, silby@silby.com, tinguely@web.cs.ndsu.nodak.edu In-Reply-To: <200305091222.h49CM9j29360@rayadm.hrz.uni-bielefeld.de> cc: freebsd-net@freebsd.org cc: ianf@za.uu.net cc: freebsd-questions@freebsd.org Subject: Re: Please, Urgent: Need ideas/help to solve PR bin/51586 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2003 14:24:15 -0000 It is interesting that your original problem report bin/51586 has problem with the same port (623) that is giving problems in this trace.: machine1 trace: 14:13:08.046004 vscan1.623 > odie.961: S 3379784543:3379784543(0) 14:13:08.046030 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544 (missing tcpdump entry of a SYN from vscan?) 14:13:11.038115 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544 14:13:11.044130 vscan1.623 > odie.961: S 3379784543:3379784543(0) 14:13:11.044147 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544 14:13:14.244139 vscan1.623 > odie.961: S 3379784543:3379784543(0) 14:13:14.244163 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544 and so on machine2 trace: 14:13:08.047366 vscan1623 > odie.961: S 3379784543:3379784543(0) 14:13:11.045502 vscan1623 > odie.961: S 3379784543:3379784543(0) 14:13:14.245542 vscan1623 > odie.961: S 3379784543:3379784543(0) and so on could there be something in your network that is eatting the port 623 packets? I would suggest crafting a connection from vscan1 port 623 to a port on odie and see if it can connect. A network analyzer or tcpdump from machine on the networks that vscan1 and odie are locate upon to see if the traffic made it over the router/switch/hub that is between these two devices. --Mark Tinguely.