2 Routers - "Nested" with same subnet

Toggle sidebar Toggle sidebar
pr3dict

pr3dict

Distinguished
Sep 22, 2011
37
0
18,530
This is about to get complicated but I'll try to keep it simple and clearly explained.

WAN from provider ----> WANRouter1

Router 1: 192.168.1.1
Port 1 - PC1 - 1.10
port 2 - Printer1 - 1.11
port 3 - PC2 - 1.12
Port 4 - Router2 - 1.2

Router1 LanPort4 ------> WANRouter2

Router2: 192.168.1.2

Port 1 - PC4 - 1.13

-----------------------------

Is this possible?


I basically want to be able to keep multicasting available to PC3 so that if it wants to find PC2 or a printer connected to router1 it can. Now, the reason I'm not using a switch is because router1 also has a vpn running on it so that it tunnels particular ports coming from pc3 through the vpn and the rest it gives back to router 1... I can't seem to figure out though if it will still allow for multicast traffic and everything else back and forth?

BTW this is all theoretical. I haven't done it yet.

Thoughts?



The reason I
 
Solution
B
If it really needs multicast you are not getting much support on consumer routers. There are huge issue just getting multicast to work between wireless and wired on the same router on some devices. It works on most because it is acting as a stupid switch and can ignore it.

The only simple way I can think of is to place all the devices behind the asus and in effect use the fios box as a modem...even though I think you must leave it a router if you have any tv service.

I have never done on a wrt platform but you should be able to run what is called a router on a stick. The wan and the lan interface would be the same interface. It makes your head hurt if you think about it too much.

So you would assign router 2 lan ip as you...
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,283
2,743
125,640
I do not see PC3 in your post do you mean PC4.

A router by definition sit between different subnets. It will not be possible to configure devices on 2 different sides of the router into the same subnet. You can of course use 192.168.2.x instead and put the proper routing in router1. This should allow the machines to communicate.

Multicast tends to be a little tricky. On a lan subnet it uses IGMP to work when you need to cross a router boundary you must load PIM. Most times I would run PIM sparse mode but if you only have a small network PIM dense mode will be fine.

.............Now I am assuming that you are running commercial routers here and you really know what multicast is.
 
Upvote 0 Downvote
pr3dict

pr3dict

Distinguished
Sep 22, 2011
37
0
18,530


I am using a verizon fios actiontech router as router 1 and an asus n66u that will have ww-drt as router 2.

I am saying multicast as I believe that DLNA uses multicast to find find all the clients for each other.

My end all goals which I think are starting to become impossible is.


    1.All media clients to be able to access each other gracefully
    2.Router 2 to specify which traffic goes through the VPN and which goes through the default gateway that is connected to Router1

 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,283
2,743
125,640
If it really needs multicast you are not getting much support on consumer routers. There are huge issue just getting multicast to work between wireless and wired on the same router on some devices. It works on most because it is acting as a stupid switch and can ignore it.

The only simple way I can think of is to place all the devices behind the asus and in effect use the fios box as a modem...even though I think you must leave it a router if you have any tv service.

I have never done on a wrt platform but you should be able to run what is called a router on a stick. The wan and the lan interface would be the same interface. It makes your head hurt if you think about it too much.

So you would assign router 2 lan ip as you indicate 192.168.1.2. Cable them lan to lan. You would set the default gateway to be 192.168.1.1. You would set pc4 or whatever to use 192.168.1.2. The traffic would go 192.168.1.2-->192.168.1.1---internet. Not real efficient but it works. The hard part now is the vpn. You would form a tunnel from 192.168.1.2 to some device on the internet letting router 1 nat the ip. You could then put in routes to send certain ip though the tunnel rather than to router 1. The nasty part is the routers know the physical interface and the vpn interface are the same interface so the traffic is going in and out the same interface and may complain. On wrt all this is done with the iptables command. I can't begin to tell you how you can configure it......I do know it can be done though because I have seen it. I have done this on many commercial cisco and juniper devices but it was easy compared to the spaghetti mess iptables is.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom