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.
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.
126.96.36.199 is not your real ip address, well not as far as the outside world is concerned. Thats just how computers on your local network see it, because your internet provider will only give you one, and you need a way of splitting it up. To find out your ip address you can go to www.whatismyip.com and it will tell you.
If you want your friend to connect from somewhere outside your local net work you have a couple of options. A way to start is to go to that website every time and just tell him what it is. This will help you get your server up but sucks when you want to actually start using it.
What I would use is called dynamic DNS. Since the IP your ISP gives you is subject to change, you need something to check it when you boot your computer, and at certain intervals. After checking it you can associate with a name that won't change.
I use the client from dynu.com on my windows machine, and I know they have a client for linux, and I haven't tried it, but I may in the next few days.
Anyway, once you get that setup, you will have a name that will point to your ip address, whether it changes or not. However if you have a bunch of computers behind a router, the name will point to the router, not your computer. (at least thats the way it works with dynu's client) So THEN you have to tell your router where you want it to send ftp requests. Thats called port forwarding, and most newer routers have it built in.
You would tell your router to forward any request over port 21(or whatever your using for ftp) to port 21 on 188.8.131.52
cause thats how your router is gonna see your computer
I hope this helps, and I haven't made horrible assumptions about your setup that lead to useless information.
You go to the routers admin page via your web browser, probably 192.168.1.1 or 192.168.0.1, and add an appropriate entry to the port forwading section, once you get to the right page just bang in the ip address of the internal ftp server and the tcp port number 21.
Check aswell you don't have any firewall blocking port 21 on the Mandrake machine and appropriate hosts.allow / hosts.deny entries if applicable.
Normally when I connect to an ftp server with a user name I put the entry in my browser like so:
If you want to be able to use passive mode (PASV) you will need to define a range of ports (high, non-privileged ports), about 50 ports in a row will do if you don't expect heavy traffic, to be used for data transfers. Set up your router to forward these ports too. If you don't it's very likely that when a client tries to connect from the outside he can get in without any problems, but a timeout will occur when listing directories or trying to download files.
Hi... I have a somewhat similar problem... I have an ADSL connection to the internet. I used the site that lil_slice gave to check my ip address which turned out to be 184.108.40.206. I set up vsftpd to allow anonymous connections. Now thru the command-line ftp client i run the command open 220.127.116.11, it gives me the following information:
Connected to 18.104.22.168 (22.214.171.124).
220 PRTC.net FTP version 1.0 ready at Sun Jan 2 04:25:14 2000
Now, this means that the IP is valid... But now, I type in anonymous as the username, and it asks me for a password (which i understand it shouldn't).. I type anonymous as well for the password, and alas, I cannot connect. Now, above it says PRTC.net. PRTC.net is my ISP. I hate to think the IP address given to me by the website provided by lil_slice is actually the IP of my internet service provider, and not of my single computer. Perhaps my computer is connected to a router used by my DSL provider?
Distribution: Red Hat 7.3, Red Hat 9, Solaris8, Slackware 10, Slax on USB, AIX, FreeBSD, WinXP, AIX, Ubuntu
mmmm... strange thing happening here....
I wonder a few things, please answer them before we continue?
Your ftp server, is it behind a firewall or NAT device, such as your adsl router? If so, what is it's internal IP Address? And next: have you tried to connect with ftp on it's internal address? Or even tried: ftp localhost on the machine itself?
there are 2 ways an ftp data connection is established. When you start an FTP session, a control connection will be made at port 21. If a client wants to transfer a file, or directory listing, another connection will be made, based on your settings. This design of the FTP protocol causes a lot of problems.
port/active mode: your ftp machine will contact the client's system. this will always work with your router, since it's just another outgoing connection. The firewall/router of the client system must support this; they must allow, and maybe forward the incoming connection.
passive mode: the client doesn't have to deal with any problems, but your system has. Your firewall should allow the incoming connection, and if you use a router, it should forward this incoming connection.
I once had a nice draytek router; this device monitored my FTP connection, and did everything automatically. My new acatel router doesn't do these things, and I need to help it a little. (ie: specify a certain port range the serer should choose for for passive mode, and forward that entire range to your internal machine)
hope this helps
(since you gave an internal IP-address for your machine, I'm almost sure you're having some sort of adsl router, or other gateway that shares the internet connection)
Ok....I agree I was making a big blunder by trying my own local IP address in the browser. But now, I have also noted down my IP from www.whatismyip.com and when I try to connect using this IP address (126.96.36.199) , it displays a 'connection was refused' error message.
I have disabled iptables too. However, I have confusion regarding one point-
I dont know what values should I give for the following:
When I try the IP that I got from whatismyip.com (188.8.131.52), it dosent work...I get the error 'connection refused'.
When I use my local IP (192.168.1.10) and use the same IP value for listen_address and pasv_address, it connects locally from my machine.