SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Distribution: slack current with 188.8.131.52 (still off the hook)
Need to force Proftp in passive mode by default
I have a problem with proftpd (1.3.0), I need to start it in passive mode but the PassivePorts directive in the proftpd.conf doesn't do the trick.
Ok here is the scenario, I set up a ring of 42 servers with several sites on each server, the apache is generating independent logs for each server and we bought a dynamic software that will retrive the logs and analize them by prefix(site), now the darn software connects through ftp but doesn't handle active mode transfer and I cannot force it to send the passive command so I need to set the proftp as passive by default. I google quite a bit and I read all the directives for the proftpd.conf and I found nothing.
Any idas, hits, suggestions are more than welcome.
Thanks in advanced.
By the way, there is not a port problem. I'm pretty sure that security/port issue has been looked upon carefully, even doe all suggestions welcome.
Yeah, when I have a problem with a particular app, I tend to read the mailing list and forums for that app before coming to a generic forum, like this one.
I've posted on the ProFTPd list in the past and got my issues addressed. I can't guarantee someone will tell you how to do what you need but you should be able to get more pertinent info regarding the feasibility of what you're wanting to do.
Since the solution hasn't been posted to the archive yet, I'll post it here:
Originally Posted by ProFTPd mailing list
> I need to set the passive mode on the proftpd server as default, but as
> > far as I have been able to read on the internet and the docs on the
> > www.proftpd.org there is not such an option. I wonder if there is some
> > sort of work around that can do the trick.
> > I'm currently running 1.3.0 and the problem is that certain automated
> > ftp client that I do not have control can access the server in passive
> > mode but I cannot force it to send the command.
Unfortunately there is no way to set a default for this. Whether the data
transfer is to be active or passive is, by RFC, left to the client to
At most, you can configure proftpd to use active data transfers only by
denying the PASV commands from clients, e.g.:
<Limit EPSV PASV>
Alternatively, you can cause proftpd to use passive data transfers only:
<Limit EPRT PORT>
However, I'm not sure that either of these configurations will help in
There might be follow-on discussion in that mailing list thread, which is why you should either subscribe to the mailing list or monitor the archives.