More woos, less, woos, but I am making progress. I finally decided to ditch gentoo for real this time. I re-installed it with an updated kernel and I just could not get rid of the following message:
!!! Block 303 is not a valid root device
I didn’t feel like dealing with the troubleshooting that one. So, after the release of the latest Ubuntu version, I decided to roll with that. After a quick look at how to forge – the perfect Ubuntu server, I was up and running in no time. LAMP, ssh, and ftp are all following suit as initially proposed. My goal no is to get get remote access with all three servers with some help from a free no-ip.com account. This dynamic dns stuff is pretty neat. Ubuntu has a built-in package for no-ip.com called….you guessed it….no-ip. All I have to do was run the following command, follow the directions, enter in my account information and I was all set.
sudo apt-get install no-ip
It automatically adds it to the start up scripts. Now, this is where I ran into trouble. I also found out my router has a built-in application for dynamic dns. My question at this point was do I use one, the other, or both? First I need to configure port forwarding on my router. 80 to 80, 22 to 22 to my local ubuntu server – 192.168.0.111. I try all three options and I get nothing. At this point I can ping joef.no-ip.org and the public ip address and get a response. So I know its out there resolving the ip address properly, it just cant connect to the server.
So, to add add more confusion to the matter, I forgot that I have a separate router that doubles as a modem for my dsl line. until not that long ago, I didnt even realize this thing was a router, a wireless one at that. The cable guy set it up and I never gave it a second thought. Just plugged in my d-link and was on my way.
So now I have way too many variables in the mix, it really could be a shit load of things. I then try to set up port forwarding on my dsl router. That doesnt seem to work. My mentality was that I can forward port 80 to the dlink, then forward that on to the server. According to what I read on the internet, things dont work that way. At this point, I am tired and I want to go to bed.
Then today, at work, I am sitting there pondering this and it hits me – PLUG THE SERVER INTO THE DSL ROUTER!!!! Wow, why the shit didnt I think of this before? So I get home from work connect the server to the dsl router. It gave it an ip address right away. I configure port forwarding for the web server, restart the router, check http://joef.no-ip.org and it works. How refreshing. If there is one thing I am learning from this its how little I know about networking.
So, as my list gets smaller I have the following to go:
- ssh – to connect to the box remotely
- ftpd – send files to and from
- samba – share files locally (still debating)
- subversion – version software projects
After this I guess its onto configuring samba and getting some shared folders going across then network. I guess goonies really don’t die.