Creating a connection between 2 routers

[siituser]

Hi there,

My home network works like this:
Cable modem to a hub - this breaks my connection to a) a NetGear router (my VPN into my external office) and b) to a Linksys router. These 2 routers go into a switch that feeds the rest of my house.

Far, far away (upstairs) I have yet another switch that divides my line to feed 3 other PCs. I have added a D-Link wireless router to this for a my new laptop. I'm runnning a windows workgroup internally for file and print sharing.

The Linksys router has an IP of 192.168.1.1
The D-Link router has an IP of 192.168.0.1

How can I create a tunnel/connection from the laptop using the D-Link wireless to a computer on the other IP range?

I hope I've given enough info - thanks in advance.

Kevin

 

[bcastner]

Not sure why you have it configured this way.

Modem --> d-Link router --> switch #1 --> switch #2
The upstairs wireless router can be configured in AP only mode:

http://www4.tomshardware.com/network/20030716/index.html

Sell the hub and surplus Linksys router from downstairs on e-Bay.

 

[siituser]

Why I have it configured this way is not the concern.

I want to know how to create a connection to between the 2 routers. Change IP addresses? Maybe there is some configuration tables to use? Something along these lines.

My apologies for giving to much information.

 

[bcastner]

My original suggestion implied that all the routing devices would be placed in the same network segment, with a single DHCP server.

This still strikes me as a sound solution for the level of routers you are using. You can preserve your VPN, and your Windows Networking.

Formally, this is handled with VLANs and a Level 3 capable switch/router at the front end. For the router class you are implementing there is no good solution other than using a single network address schema.

While I think you could do something about the VPN issue for a single client, the other aspects would require the use of LMHOSTS files for every client (in the absence of a true Windows Server product that could use WINS or DNS). There is no other way to handle the essentially broadcast nature of Netbios and Windows Networking LANS implemented on different network subnets.