Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
Connected to router
IP via static DHCP (192.168.0.100)
LFS-4.1 linux FTP server
running Pure-FTPd 1.0.14
server starts on system startup
IP is static (192.168.0.254)
this machine on router's DMZ
command used to start PureFTPd-
/usr/sbin/pure-ftpd -B -E -u 500 -l unix -A -p 60000:61000 -P mikeville.us -S0.0.0.0,21
The problem occurs when I access the server from the internet through my domain name.
The problems occur when I try to do a listing of stuff in the current directory. These problems only happen when trying to connect through the domain name. If I connect through local IP, everything works fine.
If I use a Windows client to connect to the domain name (AceFTP Freeware 3) I can connect no problem. It uses PASV and uses a port in the specified range. If I try to connect from the same machine but with XP's command line ftp, it tries to do a PORT command and stalls (I never let it give a message, but I know it won't work because it gives a local ip instead of my cable modem's). If I use ncftp on the server itself, and connect to itself, it gives a correct ip (my cable modem's), a correct port, but I get 2 connection refused messages.
I have talked with my cable internet provider (Astound in St Cloud MN) and they say they don't block any ports so that's not my problem.
I guess I have 2 questions-
1. Why does the Windows client connect correctly using PASV but ncftp on linux doesn't?
2. How do I make the server give my cable modem's ip for clients that want to use the PORT command?