Rajesh Fowkar forced the electrons to say:
> The main thing for which we may need this is say We develop a package to be
> used by pc's at location B but we want to centralize data at location A.
If the package is based on Windows, you *might* need a VPN. Else,
read on...
> How all the machines at location
> B should be configured ? One machine which connects using the leased line and
> the remaining 9 machines will connect to this machine ???
Keep one machine on location B as a router (say B1). Its eth0 will serve
the LAN, and eth1 will go on the leased line. Use different subnets on
both sides - let us say 192.168.B.0/24 at B, and 192.168.A.0/24 at A.
Set up IP forwarding on B1 -
echo 1 > /proc/sys/net/ipv4/ip_forward
Set up routing on B1 so that all packets from 192.168.B.0/24 meant for
192.168.A.0/24 go to eth1 -
route add -net 192.168.A.0 netmask 255.255.255.0 dev eth1
Set up all machines to use B1 as their gateway for the A network - in linux,
route add -net 192.168.A.0 netmask 255.255.255.0 gw 192.168.B.1
(In Windows, open the properties of Network Neighbourhood, select TCP/IP
and there is a tab to setup a gateway).
Maintain a similar setup on the gateway to the A network as well. Now,
from any of the B computers, you should be able to ping/telnet the
computers at A. Put all those commands in a file and call it while bootup.
Binand
----------------------------------------------
An alpha version of a web based tool to manage
your subscription with this mailing list is at
http://lists.linux-india.org/cgi-bin/mj_wwwusr
