From owner-freebsd-questions Mon Sep 18 17:41:37 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.monochrome.org (monochrome.org [206.64.112.124]) by hub.freebsd.org (Postfix) with ESMTP id 4707037B422 for ; Mon, 18 Sep 2000 17:41:34 -0700 (PDT) Received: from localhost (faro [192.168.1.7]) by mail.monochrome.org (8.9.3/8.9.3) with SMTP id UAA40199 for ; Mon, 18 Sep 2000 20:41:33 -0400 (EDT) (envelope-from chris@monochrome.org) Date: Mon, 18 Sep 2000 20:41:33 -0400 (EDT) From: Chris Hill X-Sender: chris@localhost To: FreeBSD Questions List Subject: Weirdness with ports & ftp/fetch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm experiencing an odd problem with ftp and fetch, specifically when I try to build a port. It seems that I can't ftp outside my home net. FTP worked earlier and I don't think I've changed anything that would affect it. I did install apache yesterday, but it's not running right now (that's apache 1.3.12, built manually, in case it matters). Here's an example of the kind of thing I'm seeing: mail# cd /usr/ports/ftp/wget mail# make install [stuff...] >> libtool-1.3.3.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from ftp://ftp.gnu.org/gnu/libtool/. fetch: ftp://ftp.gnu.org/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: connection in wrong state >> Attempting to fetch from ftp://ftp.digital.com/pub/GNU/libtool/. fetch: ftp://ftp.digital.com/pub/GNU/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: Can't open data connection >> Attempting to fetch from ftp://ftp.uu.net/archive/systems/gnu/libtool/. fetch: ftp://ftp.uu.net/archive/systems/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: connection in wrong state >> Attempting to fetch from ftp://ftp.de.uu.net/pub/gnu/libtool/. fetch: ftp://ftp.de.uu.net/pub/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: connection in wrong state >> Attempting to fetch from ftp://ftp.ecrc.net/pub/gnu/libtool/. fetch: ftp://ftp.ecrc.net/pub/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: Can't open data connection >> Attempting to fetch from ftp://ftp.funet.fi/pub/gnu/prep/libtool/. fetch: ftp://ftp.funet.fi/pub/gnu/prep/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: connection in wrong state >> Attempting to fetch from ftp://ftp.leo.org/pub/comp/os/unix/gnu/libtool/. fetch: ftp://ftp.leo.org/pub/comp/os/unix/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: Can't open data connection >> Attempting to fetch from ftp://ftp.digex.net/pub/gnu/libtool/. fetch: ftp://ftp.digex.net/pub/gnu/libtool/libtool-1.3.3.tar.gz: FTP error: fetch: connection in wrong state When I try to ftp manually, I get similar problems; here's an example of that: mail# ftp somehost.com Connected to somehost.com. 220 somehost.com FTP server (Version wu-2.6.0(1) Mon Feb 28 10:30:36 EST 2000) ready. Name (somehost.com:jchill): 331 Password required for jchill. Password: 230 User jchill logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> cd public_html 250 CWD command successful. ftp> bin 200 Type set to I. ftp> get pages.tar local: pages.tar remote: pages.tar 200 PORT command successful. 425 Can't build data connection: Connection timed out. However, I can download via Netscape with no trouble (using ftp:// URLs); and I can ftp within my internal (RFC1918) network with no trouble. The system from which I'm trying to do this (hostname mail, above) is running: mail# uname -a FreeBSD mail.monochrome.org 3.3-RELEASE FreeBSD 3.3-RELEASE #0: Sun Mar 19 15:12:55 EST 2000 jchill@mail.monochrome.org:/usr/src/sys/compile/MAIL i386 It's also doing NAT and running ipfw as well as acting as a gateway for the internal net. Again, I don't think anything significant has changed since the last time I successfully ftp'd something. Any input would be greatly appreciated; thanks very much. -- Chris Hill chris@monochrome.org [1] Bus error netscape To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message