From owner-freebsd-questions  Thu Jan 27 18:13:11 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96])
	by hub.freebsd.org (Postfix) with ESMTP id 2C01614E71
	for <freebsd-questions@freebsd.org>; Thu, 27 Jan 2000 18:13:07 -0800 (PST)
	(envelope-from freebsd@sasknow.com)
Received: from localhost (freebsd@localhost)
	by sasknow.com (8.9.3/8.9.3) with ESMTP id UAA55738
	for <freebsd-questions@freebsd.org>; Thu, 27 Jan 2000 20:13:52 -0600 (CST)
	(envelope-from freebsd@sasknow.com)
Date: Thu, 27 Jan 2000 20:13:52 -0600 (CST)
From: Ryan Thompson <freebsd@sasknow.com>
To: freebsd-questions@freebsd.org
Subject: FTP: 425 Can't build data connection: operation timed out
Message-ID: <Pine.BSF.4.10.10001271959170.55593-100000@sasknow.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi all;

Having a strange problem with a 3.2-R system and FTP.

The 3.2 system acts as a router/firewall for an internal 3.4-STABLE
system.  Haven't rebooted either machine in quite some time.  The router
(connected directly to the outside network) can, as of a couple days ago,
no longer make FTP PORT connections on outside systems!  When I FTP to a
machine on my LOCAL network (through a separate network interface),
everything works well.  When I FTP FROM another machine on the LAN,
THROUGH the router, to an outside host, everything works well.

However, when I ftp from the router machine to a remote host, I can
connect fine, see any relevant ftp server welcome messages, etc, etc...
but something as simple as an 'ls' reports:

ftp> ls
200 PORT command successful
<3-4 minute delay>
425 Can't build data connection: operation timed out

I'd rather not issue a reboot to this machine... I've tried stopping and
restarting inetd, as well as many of my non-sandboxed daemons.  ifconfig
-a output looks as it did before, and other network services appear to be
unaffected thus far.  This is really causing problems with mirroring,
though :-)

Could something be happeneding with routing, here?  Everything else
appears to work, but I've even tried flushing my routing tables and
reconstructing, but I'm still having the same symptoms.

I guess if nothing resolves it, I'll try a reboot... But I *really* don't
want to go that way :-)
 
--
  Ryan Thompson <ryan@sasknow.com>	50% Owner, Sysadmin
  SaskNow Technologies     		http://www.sasknow.com
  #106-380 3120 8th St E   		Saskatoon, SK  S7H 0W2



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message