4cca7cf0
From: gah@ugcs.caltech.edu
Mark Budzinski wrote:
> I'm not sure if I have posted this question to the appropriate group.
> If that's the case I sincerely appologize.
> I have a VPN set up between my home and my office, which I have tested
> and is working fine. However, on the office side, I have two subnets
> set up. The computer at home cannot see one of the subnets. Here is
> the situation:
> 192.168.1.0 <- Subnet at home visible everywhere
> 192.168.3.0 <- Subnet at work visible everywhere
> 192.168.2.0 <- Secondary subnet at work, not visible from 192.168.1.0
Traditionally, this was done with dynamic routing protocols like RIP.
In the case of a single home net with only one way out to the
Internet, a single static route to the router is enough. In your
case, that isn't enough. The machines on the home network need
routing table entries indicating that the not visible network
can be reached through the visible work network.
> Both my VPN routers are Linksys/Cisco RV042.
As far as I know, the RV042 supports RIP. Turn RIP on on
all the routers. Shouldn't that be three routers? One at each
end of the VPN, plus one between the two work subnets?
> I understand it has to do with routing tables. The problem is I am
> not sure what entries to add and where in order for this to work.
The other choice is to add static routes to all the home machines.
You have to remember to do this each time you add a new machine,
and in some cases each time you reboot a machine. RIP is probably
a better choice.
Some years ago, I had my home net routed through a 9600 baud link
to my office net, running RIP. There was a noticable delay in
the network every 30 seconds when the RIP routing table was sent.
I will presume that you have a faster than 9600 baud link.
-- glen
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
