Advanced Routing: Access Router B devices from Router A network
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
My network has two TP-Link Archer C1200 routers. Router A (main router) and Router B (router for IoT devices).
There is Ethernet cable from Router A LAN1 port to Router B WAN port. Router B is configured (operation mode) as router (not as Access point), mainly to isolate IoT devices from main network.
Router A LAN address = 10.0.0.1 / 24
Router B WAN address = 10.0.0.2 / 24
Router B LAN address = 10.0.1.1 / 24
If I connect to Router A, I can access devices on Router A network, but I can not access devices on Router B network.
If I connect to Router B, I can access devices both on Router B and Router A networks.
My assumption is that static route (under Router A Advanced routing) should be added, but I can not figure out what entry should be added.
I tried to add static route in Router A:
Network Destination: 10.0.1.0
Subnet: 255.255.255.0
Default Getaway: 0.0.0.0
Interface: LAN
When I try to ping Router B (10.0.1.1) while connected to Router A network, I receive: "Reply from 10.0.0.1: Destination host unreachable"
If I remove the static route - i receive "Request timed out".
Any ideas and/or solutions ?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Try setting a static route on router A like this:
Network Destination: 10.0.1.0
Subnet: 255.255.255.0
Default Getaway: 10.0.0.2
Interface: LAN
- Copy Link
- Report Inappropriate Content
If you want to go the way of cascading home-grade routers via LAN -> WAN, then a potential solution would be to setup the devices that are connected to router B to listen on different ports for requests and then setup respective port forwarding rules on router B.
For example: device 1 is configured to listen for requests on port 8001, device 2 on port 8002, device 3 on port 8003. After setting up port forwarding rules on router B to the respective IP addresses of the devices you should be able to access device 1 from router A via 10.0.0.2:8001, device 2 via 10.0.0.2:8002 and device 3 via 10.0.0.2:8003.
- Copy Link
- Report Inappropriate Content
Try setting a static route on router A like this:
Network Destination: 10.0.1.0
Subnet: 255.255.255.0
Default Getaway: 10.0.0.2
Interface: LAN
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
That won't work with home router because you're trying to ping behind NAT (in your case IoT devices).
See a detailed explanation - https://www.quora.com/What-IP-address-should-be-the-input-to-ping-a-computer-behind-a-NAT-network.
If you insist to ping these IoT devices then router B in AP mode is preferable.
- Copy Link
- Report Inappropriate Content
Thank you.
I wonder then, why I can ping (acceess) devices on main network (router A) when I am connected to IoT network (router B) ?
Main problem is that I can not acceess (from main network) IP cameras and NVR that are part of the IoT network
- Copy Link
- Report Inappropriate Content
Pings from B to A (or its clients) will work, but from A to B won't work because of the problem mentioned.
That's why the recommendation to avoid a double NAT in the local network.
My advice is - if you insist to separate the IoT network, then move the IPCs and NVR to router A network for easier access.
- Copy Link
- Report Inappropriate Content
If you want to go the way of cascading home-grade routers via LAN -> WAN, then a potential solution would be to setup the devices that are connected to router B to listen on different ports for requests and then setup respective port forwarding rules on router B.
For example: device 1 is configured to listen for requests on port 8001, device 2 on port 8002, device 3 on port 8003. After setting up port forwarding rules on router B to the respective IP addresses of the devices you should be able to access device 1 from router A via 10.0.0.2:8001, device 2 via 10.0.0.2:8002 and device 3 via 10.0.0.2:8003.
- Copy Link
- Report Inappropriate Content
Just a quick update - I once again tried your solution with static route and discovered that I can access my IP cameras from Router A network (e.g. via VLC player). I didnt try that before (accesing IP cameras live stream via VLC player). Last time I only tried to ping Router's B address 10.0.1.1 and received time out and assumed that IP cameras are not accesible from Routers A network.
Thank you for your support !
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1596
Replies: 8
Voters 0
No one has voted for it yet.