Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
OK, I'm running vsftpd, and having problems setting up PASV mode correctly. So, I went back to "basics", and tried to connect to the ftp server via telnet.
Now here's the strange thing. When I enter the PASV command on my local lan, I get a response, but trying remotely it just hangs. Here is a dialog, from telnetting to my server, on port 21, from my local lan:
Code:
220 (vsFTPd 2.0.7)
user anonymous
331 Please specify the password.
pass
230 Login successful.
pasv
227 Entering Passive Mode (192,168,0,1,245,237)
But, when I try remotely, I get as far as entering the pasv command, but I never get a response:
Code:
220 (vsFTPd 2.0.7)
user anonymous
331 Please specify the password.
pass
230 Login successful.
pasv
And it hangs there, never to return.
Obviously, the server is up and running, otherwise I wouldn't get the user/password prompts, and also there can't be any firewall issues, at least on the control port, 21. But why should the pasv command be any different. I'm still talking to the same control port, 21, and the responses should still be coming back on the same port as the others.
So, what could be the issue here. Is it possible that a firewall could filter out just certain commands.
But I already know exactly how active/passive FTP work.
My issue, is why the 1st few commands, sent to port 21, get the response back correctly, but the pasv command doesn't. It's travelling over the same tcp connection as the others.
* FTP server's port 21 from anywhere (Client initiates connection)
* FTP server's port 21 to ports > 1023 (Server responds to client's control port)
* FTP server's ports > 1023 from anywhere (Client initiates data connection to random port specified by server)
* FTP server's ports > 1023 to remote ports > 1023 (Server sends ACKs (and data) to client's data port)
Seems to me there is a problem with the firewall.
Did you read the link chrism01 gave you ?
Now he's posted the link, yes I already have read that.
The issue is NOT with the high ports, that are to be used by pasv connections.
It's with the connection to port 21, the control port.
I connect, I get a response. I send the "user" command, I get a response. I send the "pass" command, I get a response. I send the "pasv" command, and I get NOTHING back.
Why should a firewall be involved in the returning results of the "pasv", that it wasn't for the previous 2 commands.
I ran a tcpdump, on my server, and I see the reply, to the pasv being sent, multiple times, before I kill the client side.
Ha. It turned out to be my stupid a$$ VoIP adapter, which was sitting between my cable modem and my server. After pulling it out, everything works fine.
Why the ... can't those things be programmed to just pass ALL the traffic, in both directions, through untouched, if that's what I want.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.