Brandon Fosdick
2003-Oct-16 13:29 UTC
ftp/fetch "command not understood" on stable and current
On both stable and current I'm having problems getting ftp or fetch to connect to ftp servers (fetch can't connect to anything). I'm behind a firewall but the ftp ports are open and I'm sitting next to an HPUX box that doesn't have the same problem. All of the output below came from a 5.1-R box: 13:16 bfoz@~>uname -a FreeBSD mse.fbm.lmms.lmco.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 Here's what happens when I ftp to ftp.freebsd.org and try to do 'ls' (or anything other command for that matter)... --- Trying 2001:4f8:0:2::e... ftp: connect to address 2001:4f8:0:2::e: No route to host Trying 204.152.184.73... Connected to ftp.freebsd.org. 220 freebsd.isc.org FTP server ready. Name (ftp.freebsd.org:bfoz): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230- 230-You have reached freebsd.isc.org/ftp.freebsd.org. 230- 230-<insert some funky ASCII art here> 230- 230-This server is operated by Internet Software Consortium (ISC), 230-on behalf of the FreeBSD Project, and is serving the full 230-FreeBSD FTP archive via IPv4 and IPv6. 230- 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> ls 500 command not understood 227 Entering Passive Mode (204,152,184,73,184,121) --- At this point it sits there for a minute or so and then either provides the directory listing or disconnects due to inactivity. If it works I get: --- 200 PORT command successful. 150 Opening ASCII mode data connection for directory listing. total 8 drwxrwxr-x 3 root root 512 Apr 17 2003 pub 226 Transfer complete. ftp> --- Odly, it doesn't actually go into passive mode acording to status: --- ftp> status Connected and logged into ftp.freebsd.org. No proxy connection. Gate ftp: off, server (none), port ftpgate. Passive mode: off; fallback to active mode: on. Mode: stream; Type: binary; Form: non-print; Structure: file. Verbose: on; Bell: off; Prompting: on; Globbing: on. Store unique: off; Receive unique: off. Preserve modification times: on. Case: off; CR stripping: on. Ntrans: off. Nmap: off. Hash mark printing: off; Mark count: 1024; Progress bar: on. Get transfer rate throttle: off; maximum: 0; increment 1024. Put transfer rate throttle: off; maximum: 0; increment 1024. Socket buffer sizes: send 32768, receive 65536. Use of PORT cmds: on. Use of EPSV/EPRT cmds for IPv4: on (disabled for this connection). Command line editing: on. Version: lukemftp 1.6-beta2 ftp> --- That's not too bad, I can deal with waiting a few minutes for results, but about half the time I get kicked, which is annoying. My biggest problem is with fetch, it just can't get to anything at all which makes installing ports a real PITA. I'm getting a "Host not found" error but nslookup seems to think my DNS server is working just fine since I can always lookup the hosts I'm trying to connect to. I know the files are there because I can see them with ftp (when it works). A few example fetch runs... --- >> openmotif-2.2.2.tgz doesn't seem to exist in /usr/ports/distfiles/openmotif. >> Attempting to fetch from ftp://openmotif.opengroup.org/pub/openmotif/R2.2/tars/. fetch: ftp://openmotif.opengroup.org/pub/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found >> Attempting to fetch from ftp://ftp.opengroup.org/pub/openmotif/R2.2/tars/. fetch: ftp://ftp.opengroup.org/pub/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found >> Attempting to fetch from ftp://ftp.kddlabs.co.jp/X11/openmotif/R2.2/tars/. fetch: ftp://ftp.kddlabs.co.jp/X11/openmotif/R2.2/tars/openmotif-2.2.2.tgz: Host not found >> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/openmotif/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/openmotif/openmotif-2.2.2.tgz: Host not found >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/openmotif and try again. --- 13:12 bfoz@~>fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages/All/nedit-5.3.tbz fetch: ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages/All/nedit-5.3.tbz: Host not found 13:16 bfoz@~>nslookup ftp.freebsd.org Server: ddns2.lmms.lmco.com Address: 129.197.11.4 Non-authoritative answer: Name: ftp.freebsd.org Addresses: 204.152.184.73, 62.243.72.50 13:16 bfoz@~> --- Other, non-FreeBSD, unix boxes on the same network can connect just fine and I can't seem to find any significant configuration differences. Maybe I just don't know what I'm doing. Here's the status output from an HPUX box... --- bfosdick@hp281:/home/bfosdick<2> ftp ftp.freebsd.org Connected to ftp.freebsd.org. 220 freebsd.isc.org FTP server ready. Name (ftp.freebsd.org:bfosdick): anonymous 331 Guest login ok, send your complete e-mail address as password. Password: 230-You have reached freebsd.isc.org/ftp.freebsd.org. 230- 230-<insert some funky ASCII art here> 230- 230-This server is operated by Internet Software Consortium (ISC), 230-on behalf of the FreeBSD Project, and is serving the full 230-FreeBSD FTP archive via IPv4 and IPv6. 230- 230 Guest login ok, access restrictions apply. Remote system type is UNIX. Using binary mode to transfer files. ftp> status Connected to ftp.freebsd.org. No proxy connection. Mode: stream; Type: binary; Form: non-print; Structure: file Verbose: on; Bell: off; Prompting: on; Globbing: on Store unique: off; Receive unique: off Case: off; CR stripping: on Ntrans: off Nmap: off Hash mark printing: off; Use of PORT cmds: on ftp> --- Any ideas? -Brandon
Scot W. Hetzel
2003-Oct-16 20:06 UTC
ftp/fetch "command not understood" on stable and current
From: "Brandon Fosdick" <brandon.h.fosdick@lmco.com>> On both stable and current I'm having problems getting ftp or fetch to > connect to ftp servers (fetch can't connect to anything). I'm behind a > firewall but the ftp ports are open and I'm sitting next to an HPUX box > that doesn't have the same problem. > > All of the output below came from a 5.1-R box: > 13:16 bfoz@~>uname -a > FreeBSD mse.fbm.lmms.lmco.com 5.1-RELEASE FreeBSD 5.1-RELEASE #0: Thu > Jun 5 02:55:42 GMT 2003 > root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC i386 > > Here's what happens when I ftp to ftp.freebsd.org and try to do 'ls' (or > anything other command for that matter)... > --- > Trying 2001:4f8:0:2::e... > ftp: connect to address 2001:4f8:0:2::e: No route to host > Trying 204.152.184.73... > Connected to ftp.freebsd.org. > 220 freebsd.isc.org FTP server ready. > Name (ftp.freebsd.org:bfoz): anonymous > 331 Guest login ok, send your complete e-mail address as password. > Password: > 230- > 230-You have reached freebsd.isc.org/ftp.freebsd.org. > 230- > 230-<insert some funky ASCII art here> > 230- > 230-This server is operated by Internet Software Consortium (ISC), > 230-on behalf of the FreeBSD Project, and is serving the full > 230-FreeBSD FTP archive via IPv4 and IPv6. > 230- > 230 Guest login ok, access restrictions apply. > Remote system type is UNIX. > Using binary mode to transfer files. > ftp> ls > 500 command not understood > 227 Entering Passive Mode (204,152,184,73,184,121) > --- >Your ftp client went into passive mode. The reason it went to passive mode is because the /etc/login.conf file is setting an environment variable ((FTP_PASSIVE_MODE=YES) to turn on passive mode. To disable it, run ftp or fetch under sh as follows: FTP_PASSIVE_MODE=NO ftp ... FTP_PASSIVE_MODE=NO fetch ... or change FTP_PASSIVE_MODE to NO in the "default" section of /etc/login.conf, and then use cap_mkdb /etc/login.conf to rebuild the login.conf.db. Scot
Kevin D. Kinsey, DaleCo, S.P.
2003-Oct-16 20:25 UTC
ftp/fetch "command not understood" on stable and current
Scot W. Hetzel wrote:>Your ftp client went into passive mode. The reason it went to passive mode >is because the /etc/login.conf file is setting an environment variable >((FTP_PASSIVE_MODE=YES) to turn on passive mode. To disable it, run ftp or >fetch under sh as follows: > >FTP_PASSIVE_MODE=NO ftp ... >FTP_PASSIVE_MODE=NO fetch ... > >or change FTP_PASSIVE_MODE to NO in the "default" section of >/etc/login.conf, and then use cap_mkdb /etc/login.conf to rebuild the >login.conf.db. > >Scot > > >Alternatively --- $ftp ftp>pasv passive mode off. ftp>open ftp.freebsd.org ....etc.....