Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My home network setup looks like this:

My home network setup

Both routers are TP-Link TL-WR1043ND routers. The basement router handles all devices in the house that are connected via cable, handing out addresses for the 10.89.49.0/24 network via DHCP. Wireless doesn’t really work from the basement, as the signal is too weak, so I have disabled it.

To do WiFi, I have added a second (identical) router downstairs. On the WAN side it is assigned the 10.89.49.101 IP address from the basement router, and on its LAN it provides the 10.89.7.0/24 network. Basic internet access works flawlessly from any device this way.

I am now facing the problem that I am not able to communicate (e.g. SSH) between all devices, wired or wireless. I am able to connect from a wireless device to a wired device, for example SSH-ing from 10.89.7.X to 10.89.49.Y, but it doesn’t work the other way round—despite the fact that I have added a static route to the basement router:

Static route configuration on the basement router

Does anybody have any idea on how to solve it? Both routers have already been upgraded to use the most recent firmware from TP-Link.com (Build 110429), to no avail.

Errata: I would like to stick with the official firmware, switching to something like DD-WRT or OpenWrt only as a last resort.

share|improve this question
    
Shouldn't the static route point to 10.89.49.0/24, so traffic from the basement router knows where the upstairs router is? –  dannymcc Nov 18 '11 at 8:57
    
This makes no sense to me. The basement router already handles 10.89.49.0/24, and it also provides the 10.89.49.101 IP address for the other router—so it should know exactly where the WiFi router is. –  igor Nov 18 '11 at 9:09
    
You're right, sorry! I was looking at the diagram the wrong way around - reading the basement as upstairs and vica-versa. –  dannymcc Nov 18 '11 at 11:58
add comment

2 Answers

up vote 3 down vote accepted

I know what's going on. You leave clear with the address you are using on the routers and what you say: "I am able to connect from a wireless device to a wired device, for example SSH-ing from 10.89.7.X to 10.89.49.Y, but it doesn’t work the other way round" The way you have set it up, doesn't allow it.

Since you wanted all devices to communicate with each other, you shouldn't have them in different LANs rather use the same for all devices. So you network arquitecture approach failed there.

Let Router1: be the router directly connected to the internet Router2: be the other one.

What I would do is disable the LAN DCHP Server on the Router2 and change the cable from WAN to LAN. (Cap WAN port) Also, give it (Router2) a Router1 LAN IP Address on its LAN port, so you will be able to get to it via its HTTP Server

share|improve this answer
    
That does it, thanks! –  igor Apr 24 '12 at 9:10
add comment

The first thing I would suggest is plug in a test machine into the internet-connected router. Manually give it an IP and set a route on it to the other router.

If you have Linux, it would be something like this: ip addr add 10.89.49.x/24 dev eth0 ip link set up dev eth0 ip route add 10.89.7.0/24 via 10.89.49.101 dev eth0

Then try pinging 10.89.49.101 (to verify you can hit the wan interface of your router) and then try pinging something beyond it like 10.89.7.1.

If you can't find .1, it's probably a NAT or Firewall issue. Firewalling may be preventing traffic from the WAN interface from reaching the LAN. Unless you have a reason to enable it, I would consider disabling the all firewalling on the device. (Hopefully the manufacturer supports that).

Lastly, check if the router has NAT settings. If NAT is enabled it may be expecting you to explicitly set forwards for ports on 10.89.7.101 to machines and ports in 10.89.7.0/24.

If you don't have a Linux test machine, consider downloading a Live CD to do the testing or someone else can comment and tell you how to do that in Windows.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.