Guys,

You have plenty of concepts in networking that are very hard to grasp.

And networking is my focus area.

In today's Internet any cool technology uses networking in some way or other.

My rich knowledge in networking helps me do several things with a lot
of constraints.

In several cases even if you pump in a lot of cash you cannot achieve
the goal you have without
 knowledge.

The main complication on the Internet is caused by NAT. Most of us
work on private IPs and you cannot
access the home machine from office and vice versa.

Unless you have a VPN.

By the way VPN also does encryption and you can access any remote
application. This is not like that.

My solution is very simple.

First what is the goal?

Today I have many clients scattered over Chennai and I have machines
at home and office.

Nearly all of them run OpenBSD and some linux. I also have a VPS in US.

The VPS runs Debian and it has a public IP that is static of course.

Now all I have to do to connect to any of the machines I run in my
client locations or home/office is this:

             a) Open an ssh remote forwarding connection to my public IP in US.

Office A:
----------------------------------------------------------------------
                       $ ssh -R 3000:localhost:22 1.23.4.47
                         <login and stay connected>

Each machine will use a different port.

So from my other client office I start port forwarding like this.

Office B:
----------------------------------------------------------------------
                       $ ssh -R 4000:localhost:22 1.23.4.47

Just replace my VPS IP(1.23.4.47) with your public IP.

Now all you have to do to access your machine in Office A or office B
is to first login to your VPS.

$ ssh 1.23.4.47

Then, access the local port that is forwarded to the remote location.

$ ssh -p 4000 localhost

for logging into office B

and

$ ssh -p 3000 localhost

for logging into office A.

This way I can access any UNIX machine anywhere through my public IP.

This also does not take up any resources. You don't need the
complexity of VPNs and you
don't need to configure anything in machines not under your control.

You can do ssh port forwarding in your BSNL MODEM by associating a
public port with a private IP and port.

But this method is much better since you won't get this access at many
places and certainly not your client offices.

Another thing is that this MODEM port forwarding/DNAT/ TCP redirection
works only for one machine.

Whereas with our idea we can access any number of machines behind the
same MODEM.

Sorry if this was too complex.

You need a lot of context to follow this cool idea.

Thanks.

Ever yours,
Girish

-- 
Gayatri Hitech
web: http://gayatri-hitech.com

SpamCheetah Spam filter:
http://spam-cheetah.com
_______________________________________________
ILUGC Mailing List:
http://www.ae.iitm.ac.in/mailman/listinfo/ilugc

Reply via email to