From owner-freebsd-chat Mon Oct 30 23:20:30 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id F0C8E37B479 for ; Mon, 30 Oct 2000 23:20:27 -0800 (PST) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id AAA27096; Tue, 31 Oct 2000 00:16:44 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp02.primenet.com, id smtpdAAApeaGZ0; Tue Oct 31 00:16:35 2000 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA26392; Tue, 31 Oct 2000 00:20:08 -0700 (MST) From: Terry Lambert Message-Id: <200010310720.AAA26392@usr02.primenet.com> Subject: Re: ftp.freebsd.org b0rked? To: des@ofug.org (Dag-Erling Smorgrav) Date: Tue, 31 Oct 2000 07:20:08 +0000 (GMT) Cc: dg@root.com, chat@FreeBSD.ORG In-Reply-To: from "Dag-Erling Smorgrav" at Oct 30, 2000 08:33:31 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > No. It doesn't care about reverse DNS or what you typed in above. I don't > > know why the connection was closed. Have you tried it more than once? Does it > > still do that now? > > Yes, and yes - it consistently drops connections from this net, but it > works fine from other places. I'm starting to wonder if there's a > transparent proxy somewhere upstream that's screwing the pooch. > > Might there be some relevant information in the ftpd logs on > ftp.freebsd.org? The hosts that fail to connect are all on the > 193.212.248.0/25 subnet. I have seen this with particular firewalls (I think CheckPoint was one), where they attempt to do state tracking on FTP, and fail to be able to do that and do address rewriting at the same time. The fix was to hack the FTP daemon to use leading zeros, so that the IP address had the same number of digits before and after being rewritten. Later versions of the software didn't have the problem. There was also a problem with PPPoE that ended up being the ipfw packet drop code; there was a recent patch that went by in -current, which seemed to address this, so maybe it's just a case of old code, if you are running ipfw based firewalls on FreeBSD boxes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message