proftpd only works in standalone mode, not inetd mode (slack 10.2)
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
4. I also cannot ftp into my linux box from my windows box (both behind my router)
When ServerType is set to "standalone":
1. I can get the ftp server to work, as demonstrated here:
yimboli@yimux:~$ ftp localhost
ftp: connect: Connection refused
yimboli@yimux:~$ su root
yimboli@yimux:~$ ftp localhost
Connected to localhost.
220 ProFTPD 1.2.10 Server (ProFTPD Default Installation) [127.0.0.1]
Name (localhost:yimboli): yimboli
331 Password required for yimboli.
230 User yimboli logged in.
Remote system type is UNIX.
Using binary mode to transfer files.
2. My /etc/proftpd.conf file looks like this
# This is a basic ProFTPD configuration file.
# It establishes a single server and a single anonymous login.
# It assumes that you have a user/group "nobody" and "ftp"
# for normal/anonymous operation.
ServerName "ProFTPD Default Installation"
# Port 21 is the standard FTP port.
# Umask 022 is a good standard umask to prevent new dirs and files
# from being group and world writable.
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
# Set the user and group that the server normally runs at.
# This next option is required for NIS or NIS+ to work properly:
# Normally, we want files to be overwriteable.
# A basic anonymous FTP server configuration.
# To enable this, remove the user ftp from /etc/ftpusers.
# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp
# Limit the maximum number of anonymous logins
# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
# Limit WRITE everywhere in the anonymous chroot
# An upload directory that allows storing files but not retrieving
# or creating directories.
# <Directory incoming/*>
# <Limit READ>
# <Limit STOR>
3. I *can* ftp into my linux box from my windows box (both behind my router)
4. People outside my network *cannot* ftp into my linux box, getting this error message: DOH how do I upload an image???
This is my fourth or so time installing slackware, but I never had this problem before. It is, however, my first time installing 10.2. Any ideas as to why inetd won't work? I know, someone might say "dont fix it if it's not broken", but unless I'm mistaken, inetd is the preferred way to run proftpd, so I'd like to get to the bottom of this.
Nevermind on that last post, protfpd.conf still had ServerType set to standalone, so I changed it to inetd and restarted inetd! woohoo! so let me get this straight, if I wanna change proftpd to standalone mode, I need to change ServerType in proftpd.conf to standalone, and ALSO comment out the line about proftpd in inetd.conf, correct????
Still wondering about a one-line process restart command
Also, here's my latest FTP woe: FTP works fine if I plug the cat5e cord from my cable modem DIRECTLY into my linux box and let them figure out the IP. However, if I put my router between the cable modem and the linux box, people cannot see the contents of the folders, but they can log in. Specifically, when peter logs in with his user and pass, they are accepted as correct, and internet explorer proceeds to lag out after 300 seconds of sending directory requests (i assume they are directory requests because the only thing that ever shows up in the folder contents portion of the window is an hourglass). I have ports 20 and 21 forwarded on my router to my linux box.
Also, so you dont think I'm asking a question empty-handed, I used ethereal to capture some packets when I tried to ftp from my windows machine to the linux box using the ROUTER's ip address (in other words I think this approach mimics an outside person ftping in), and noticed that my windows box sent the request FROM its port 4049 (a random choice i think) TO port 21 on the router, which was then forwarded to the linux box. I cannot, however, figure why the connection lags out. I'm almost positive it's router-related because, like I said, FTP works like a charm if I plug my internet DIRECTLY into the linux box, but it stops when I put the router in the middle.
if I wanna change proftpd to standalone mode, I need to change ServerType in proftpd.conf to standalone, and ALSO comment out the line about proftpd in inetd.conf, correct????
As for the rest, you should use passive mode to be able to browse your ftp server, or forward also port 20 (which is the ftp data port) from the router to your ftp server. If you have done that with no success then it's maybe iptables that prevent active ftp
okay, I'll have to check those out after work... but one thing is confusing me already: passive vs. active mode. When I've logged into FTPs on my windows box, I've never had to select an active or passive mode, so I'm unclear as to how such a change helps me when I'm remotely logging in.
Also, it seems like my linux box is set up just right now, with my router being the problem. proftpd is running in inetd mode, like I want it to. And good old peter copied 155 megs of stuff last night from my FTP, but that was when my cable modem was plugged directly into the linux box. Now, however, with the cable modem going to the router, and the router going to both the linux box and the windows box, I'm having issues, even though I forward both ports 20 and 21 to my linux box.
but wait, you mentioned IP tables... now I'm wondering if that's the problem. I have no clue what ip tables are, but from the sound of it, my initial thoughts are that by adding a device with its own IP address (router), I might mess up the "ip table"?
The list of things to research grows and grows! so much to learn with linux, so little time off... i guess it would help if my job was remotely related to computer stuff.
Iptables (note: it's one word, not 2: ip tables) it's a sort of firewall installed by default in most modern linux distros, which prevents unauthorized access to your box ports. You have to "open" a port in iptables rules to be able to use that port.
Oh, now I see. I remember something about that when I had a call of duty 1 server running in slack 8.something on my college lan. Let me ask from the theoretical perspective though, if the FTP worked fine without the router, doesn't that show that there are no firewall/iptable issues? adding a router between the linux box and the internet cloud wouldn't make my *linux box* the actual problem, would it? I'm more inclined to investigate my router as the culprit.
It seems that directory requests work in command line programs (such as ftp in winxp's command prompt, or ftp in linux), but they time out in GUIs (internet explorer on my winxp, and also the gui on my friend's apple). Has anyone heard of this problem?
im pretty sure IE can only do one or the other and not both.. i think it normally is set to use passive.. if you do not have your server setup to accept passive connections.. then you will time out in IE.. there is a way to change IE im sure.. but you would be better off to use passive on the server..