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.
I wonder if anyone else has run into this problem: I set up an account with no-ip.com. I can get into my ftp server from outside by running pure-ftpd -p 50000:50100 -A -P 128.92.177.XXX & without a problem. I setup my linksys router to forward ports 50000 through 50100 to my local box.
My main problem is when my ISP decides to change my ip address. I have to telnet in, stop the server and restart it with my new IP. Is there a way to automatically do this, or maybe just use the host name (somethingstupid.serveftp.com) from no-ip?
I found a few threads on the Pure-ftpd site that had the same questions, but they went unanswered from the beginning of 2002 Someone had mentioned that they made a script that would check the current ip against the last ip that pure-ftpd was started with and if it was different the script would restart pure-ftpd with the new ip address. I have no idea how to write scripts....
noip.com has a tool that you place in your rc.local file to startup with each boot. It detects the IP, and then sends that to your no-ip account to keep it updated.
Then to connect, you just have to use the hostname, just like I have up there. That's it AFAIK.
Now unless your ISP is changing your IP more often than you reboot, this will work. If you aren't rebooting as often (which is good) then you will probably want to run the noip program as a cron or something, depending on your needs, how often.
I loaded the software from no-ip (actually, I have it running on my Win2K machine as well, just as a backup.).
The problem is if I lose my connection for whatever reason, (power outage, sometimes I have to reset the router, or my 3 year old climbing behind my desk to unplug things, etc...) I have to shut down the ftp and restart it with the new ip address.
Example, I had an IP of 184.108.40.206, when I reconnected, I got 220.127.116.11. Now I have to log into the machine either locally if i'm at home or through telnet if i'm not, and kill the ftpd process and restart it with these options: pure-ftpd -p 50000:50100 -A -P 18.104.22.168 &. It would be nice to have either a switch that would just allow the hostname or a script that could check the current public IP against the IP that pure-ftpd was started with.
If I leave the -P 22.214.171.124 option out, the server tells the client to expect a connection coming from 192.168.1.70 (the internal address) instead of the public address. Since 192.168.1.70 isn't viewable from the public internet, the FTP client just hangs and eventually times out.
The router, BTW, is a BEFSR41 v.2. I picked it up for $30 used, and it's been working fine for about 4 months. I've had to reset it once or twice, just be careful not to hold the reset button down too long or you'll lose all your settings. (It was hard enough trying to dig up my dsl account info )It's been pretty easy to setup so far.
Wow... sorry for the novella here... Have a happy, safe and prosperous 2003, and good luck with the router!
' This document is both a tutorial and a reference on shell scripting with Bash. It assumes no previous knowledge of scripting or programming, but progresses rapidly toward an intermediate/advanced level of instruction.'
Well, the forwarding part was pretty easy.
I'm using firmware version 1.43 (I'm not sure if the options will be the same on different revisions)
I set a static IP on my linux machine. (192.168.1.69).
Go into the Advanced options and then the Forwarding tab.
I actually created 2 entries here:
FTP, Ext. Port 20 to 21, both UDP and TCP are checked, the IP is set to 192.168.1.69 and the enabled checkbox is checked.
The second entry is:
FTPPasV, Ext. Port 50000 to 50100, both UDP and TCP are checked, the IP is set to 192.168.1.69 and the enabled checkbox is checked.
After that, I start pure-ftpd with these options: pure-ftpd -p 50000:50100 -A -P 126.96.36.199 &
The IP address in that command line is your external ip assigned by your ISP, the -p 50000:50100 is the ports that will be used for passive transfers. It should work then.
Oh, and UPnP is Universal Plug and play. It allows the router to open ports automatically, if the applications use it. So far the only thing I found opening ports was MSN Messenger. I disabled the option in the Passwords section of the configuration pages )