From owner-freebsd-current@FreeBSD.ORG Wed Jul 21 20:10:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B32C16A4D0 for ; Wed, 21 Jul 2004 20:10:15 +0000 (GMT) Received: from apathy.neglect.us (rapture.nine.org [69.17.66.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E4943D4C for ; Wed, 21 Jul 2004 20:10:14 +0000 (GMT) (envelope-from matt+list.sw.freebsd.current@publicly.neglect.us) Received: from [192.168.20.34] (ipffw01-dmz1.ipfabrics.com [4.18.226.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by apathy.neglect.us (Postfix) with ESMTP id CB9C5CC3 for ; Wed, 21 Jul 2004 16:10:13 -0400 (EDT) Date: Wed, 21 Jul 2004 13:10:12 -0700 From: Matt White To: freebsd-current@freebsd.org Message-ID: <3279369656.1090415412@[192.168.20.34]> In-Reply-To: <20040721115021.J81889@carver.gumbysoft.com> References: <000001c46f11$1f53a880$132a15ac@spud> <3270557515.1090406600@[192.168.20.34]> <20040721115021.J81889@carver.gumbysoft.com> X-Mailer: Mulberry/3.1.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: RE: fetch hangs, part 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jul 2004 20:10:15 -0000 I don't think so in this case since I was using this same netscreen with a FreeBSD 5.1 box without incident. I'm actually suspicious of the cabling at the moment, but I have higher priorities than to figure that out at the moment. -Matt --On Wednesday, July 21, 2004 11:51 AM -0700 Doug White wrote: > On Wed, 21 Jul 2004, Matt White wrote: > >> In my case, I tracked this down to either my netscreen5 or the cable into >> it going south. It's a bit strange because other software wasn't having >> an issue, so I'll probably look at this more in the next few days. But >> for now, removing that box from my network has made fetch happy again, >> which in turn has made me happy again. > > It might have been breaking passive-mode FTP. I've noticed this problem > coming from certain places. Thankfully not from my workplace or home :) > > Some older inspective firewalls don't understand passive mode and drop the > connection. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"