[lug] remotely accessible sub-domain

[Michael Deck]

At 10:03 AM 2/25/2003, you wrote:
>On Tuesday 25 February 2003 6:48 am, Paul Nowosielski wrote:
>> Hello,
>
>> How can I make 192.168.5.5 remotely accessible via http
>> and ssh? I would appreciate any help in this.
>>
>> Paul Nowosielski
>
>I don't think it is possible for the outside internet to 
>directly access 192.168.5.5, but you can attach a new ip 
>address to your mainbox (man ifconfig) and route http and 
>ssh packets going to the new ip address to the internal box 
>(192.168.5.5) using port forwarding (man ipchains or 
>iptables).

It's been a while since I've done this, but I don't think the new IP address is needed if you know which ports you want to forward. You can just port-forward port 80 (usual http) and 22 (usual ssh) ports of your main box directly to your internal box. If you need to open up more ports for forwarding, you just change your script and those ports go onto your internal box. The forwarding mechanism doesn't know what the packets are for, it just forwards certain ports. So if you decide you want your internal box to be an SMTP server, you just start up the SMTP daemon on the internal box and ask your mainbox to forward port 25. 

If you want to forward everything directed to a particular IP address, then Case is right -- you also need another externally-visible IP address for the main box. 

>Case Jones
>_______________________________________________
>Web Page:  http://lug.boulder.co.us
>Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>Join us on IRC: lug.boulder.co.us port=6667 channel=#colug


Michael Deck
Cleanroom Software Engineering, Inc.