I currently have a residential BT home hub (router A) as the primary router and provides Internet connectivity. I have a second router that is NOT a home hub, lets call it router B. Router B is used for LAN traffic routing. Router B is plugged into an ethernet port of the home hub. Router B is on a different ip range compared to the home hub. How can I configure the home hub to route traffic based on ip address to router B . I have searched the settings but cannot find anything. I don't want to route using port forwarding, I want to route based on Ip range (regardless of port). Routers should be able to link two different networks.
Here is the example to illustrate the above:
HH - 192.168.1.X (255.255.255.0)
ROUTER B - 10.0.2.X (255.255.255.0)
DEVICE 1 (192.168.1.10) cannot reach DEVICE 2(10.0.2.5) .
Thanks for the help
LAN port on the HH to WAN port on B. Wan port address needs to be in HH network.
Oh...and if you are going to use 10. that subnet mask needs to be 255.0.0.0 for a private network.
If he if going to use 10.0.2.x then his subnet mask at 255.255.255.0 is correct, if he was using 10.x.x.x then 255.0.0.0 would be appropriate.
So what is it that our OP is trying to do?
It's far easier to have 2 or more subnets within the same reserved range, otherwise, you have to resort to creating rules which you just can't do on most ISP-provided equipment.
There are lots of what/why possibilities, so maybe some more info from the OP would be worthwhile!
Thanks, but the issue will still be that the HH does not know how to direct traffic to Router B. The HH does not seem to have settings or an address/routing table to inform it to send 10.0.2.x to Router B
I do something similar but use 192.168.2.1 for my SH2 and my network is the 192.168.1.xxx range as that how my setup was before I was forced to use the SH2 for Digital Voice.
All I do is set the SH2 to port forward everything (IPv4/6) to 192.168.1.1 which is my router. I use 255.255.252.0 as the subnet mask.
For the SH2 it's a firewall setting for IPv4 and pinholes for IPv6.
Works perfectly for me
@countrypaul The problem is 10.0.2.x on 255.255.255.0 is a public as range. Using that in a private context has problematic written all over it and is considered bad practice. I suspect the HH may be funny about passing that over a LAN port. In fact, I'm surprised it allowed it at all.
Tim Curtis’ approach is the same as I use and works fine.
All addresses within the 10.x.x.x range are private, that means you can have one network at 10.0.2.x and one at 10.0.1.x and a router linking them and also linking to the internet. The router should not forward any of the private addresses to the Internet. Not sure how many, if any, simple ISP supplied routers could handle that. The subnet mask it used to determine if a target address is on the local network or if it needs to be sent via a router.
I agree that Tim Curtis’ approach is probably amongst the best solution though.
@countrypaul. Actually, you’re right now I think about it. Too used to seeing it used with 255.0.0.0 in workplaces.
I concede the point sir!