I have newbie question on how to remotely access one of my computers. I'm running several boxes off my DSL and would like to access my Linux system remotely (Fedora Core 1, Apache 2.0, MySQL 4.0 and PHP 4.3). I do not have a static ISP address, but it hasn't changed in the last month either. My home architecture currently is something like:


 ISP       Router     Switch & nbsp; Computers
                &nbs p;              +-- WinXP 1
Qwest ---- Cisco ---- NetGear -+-- WinXP 2
 DSL        678      &nbs p; GS108   +-- WinXP 3
                &nbs p;              +-- Intel Wireless Gateway
                &nbs p;              +-- LAMP Box


Internally the routter is dynamically assigning Class A addresses, e.g. 10.0.0.x to the various boxes. So how do I direct http (or ftp etc.) requests to the correct computer?


I read the Remote login thread (threadid=6885) but it was a bit over my head and I couldn't even tell if it was answering my question <sigh>.

TAI

With this setup, AFAIK, you can't.
A box that you're going to connect to externally needs a static IP on the local network, and the router needs to be configured to forward a given port (22 for SSH) to that machine.

So:
Configure the box in question to have a static IP
Make the router forward port 22 to the box's IP (see docs on your router for specifically how - most have an HTML interface that will let you set prefs)
connect to your router's IP remotely on port 22 and witness the magic.

--Rounan

EDIT: I'm not familiar with SQL requests, but if you also want webservice, forward port 80 to the box. SQL will use a port. don't know which. Same principle applies.

Configure your router to forward port 80 traffic to the ip address of your Linux box then make sure you are running a web server on the linux pc. You will probably want to statically assign an address to the Linux box as well.
Some ISP's block incoming Port 80 traffic, to prevent you from running a web server so if this doesn't work you may change the port that the webserver is running on to work around this. SSH = port 22 and FTP = port 21

Hey
You could be a little more secure about this ( if you care to )
Configure a machine to work through , on your internal lan.. for PCANYWHERE or
TimbuckTu, if you have a server all the more, use terminal server services to access it .
1. Configure a remote client PC could be a server ( use terminal server ) , with the password encription feature this will be the added security,
2. Set up Port mapping with your router , use the ports for what ever service you choose, if it terminal services 5631, 5632 you can serch for them on www.microsoft.com, Winxp has built in terminal server
3. use TimbuckTu ports 407 UDP, 1417-1420 for services
4. set this up on your router Nat features, to point to the internal workst or server IP
5. Use the connection to this terminal server to telnet to the local Linux box and perform anything on a more secure path.

Windows XP terminal server is not going to run well on linux.
and do you realy trust microsoft with your security !!!!!

set all the pc's on your lan's IP address statically, (not via dhcp)
and set your router o forward all ssh traffic to the ip on the linux machine.
now use the serives tool from fidora core 1's menu and make sure sshd is set to run on bootup.

now, from any machine with internet access you can login to your home linux machine with ssh.

read
man ssh

also, you may want to have an ftp server running for file transfere.
use the services tool again, the ftp daemon is called vsftpd (very secure ftp daemon)

you guys are crazy... you dont have to have a static IP (on your internal machines), just set the DHCP lease on your router to unlimited.

Why not just foward port 22 to one machine, that will give you SSH access to all linux machines.
_____________________

On the web server, I don know what you are doing, but you only have to foward to port 80 on one of the machines, and install SQL on another, it will make the sql connection from behind your router and never need to go outside port 80 (that is if you even plan to have a sql backend).

Trey, that'll work great - until you power off two computers and then power them back on in reverse order. oops, their IPs are reversed.
Static IP is a much better solution.

And yeah, once you're on the internal network, you can use the machine you've connected to to ssh to any other.

--Rounan

most routers IP address are given via mac address... I have run a dynamic setup with 4 machines for over a year now.. and they all have had the same ip (even reinstalling on a few they still get the same ip)

Huh... nifty.
I've observed the opposite behaviour with my Linksys routers.

Dah well, all hardware is not created equal.

Cheers,
--Rounan

A question about bandwidth here. The network has 6 systems on it, 3 of them 10/100, a WiFi and two 10/100/1000 NICs. If I were to route everthing from the router through another machine as a firewall, would I have to get two 10/100/1000 cards? My U2 Server only has one slot left and I'm currently using the onboard 10/100 port.

no i dont think so ... but I could be wrong