I have this situation:


The Thomson Gateway TG712 is received from provider, is a phone line/DSL modem, with 4 wired LAN (RJ45) connectors, as well as wireless. It assigns to itself, and then assigns 192.168.1.* to machines connected to it via wired or wireless.

One of the LAN ports on the Thomson (which doesn't have a WAN Ethernet port, as it uses a phone connector for that purpose) is connected with the WAN RJ45 port on the Allnet router; the Thomson sees this device as - while the Allnet sees itself as, and assigns 192.168.0.* to devices connected to it (the Allnet device is wired router only).

The machines connected to the Thomson network 192.168.1.* can ping each other, and ssh to each other (all the laptops are Ubuntus); likewise, the machines connected to the Allnet network 192.168.0.* can ping and ssh each other. My problem is - I cannot see (ping or ssh) machines on the Allnet network 192.168.0.* (Laptop D or Laptop C) from the Thomson network 192.168.1.* (from, say, Laptop A or Laptop B).

Is it possible to have machines on the Thomson network 192.168.1.* communicate with machines on the Allnet network 192.168.0.* - and if so, how? I read somewhere that what I need is "static routing", but I cannot find how to set that up on the Thomson...


The way you have it setup it will not work, your "router" is actually a router/gateway/firewall for consumer use, so many of the functions you would have to disable or change to make this work (like building static routes) are not possible.

The best way, and most efficient, could be to disable DHCP on the Allnet router, and connect a LAN port from the Thompson gateway to a LAN port of the Allnet router, making the Allnet router essentially a dumb switch, and all one subnet.

  • Thanks for this @acejavelin - will give this a try and report back; cheers! – sdaau Mar 13 '16 at 21:54
  • 1
    Are you sure? Almost all "consumer gateways" I've used had static routes as a feature, even the most stripped down ones. – grawity Mar 13 '16 at 22:11
  • 1
    @grawity No, I don't know of that router specifically but the firewall and NATing changes that would need to be done to make these 2 networks transparent to each other are not possible in most consumer class routers. There is no stated reason to have 2 distinct subnets, so making it a single subnet would be the most efficient answer. – acejavelin Mar 13 '16 at 23:27
  • Thanks again - just got the time to do this, and it works - now all PCs on local network can see each other and go on the Internet (although it required a couple of reboots/dhcp renew's after changes were made). Also, as a consequence, it seems I have missed access to the Allnet router webpage (which was at, but that doesn't matter. And just to confirm, I didn't have a reason to have 2 distinct subnets, I just had it set up like in OP because I thought that is "the way" to connect two routers and have Internet. Cheers! – sdaau Mar 20 '16 at 10:30
  • @sdaau You can temporarily set a computer to a 192.168.0.x IP and access the Alley router, then change its IP address to something like or so you can still access it, but there really isn't anything there you would need access to anymore, and if it gets redeployed again it will likely be defaulted anyway. – acejavelin Mar 20 '16 at 15:27

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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