I have "joined" two networks using 3 Routers. So far, communication to & from the Left & Right hand networks is working as I had expected.
However, the Midddleman (192.168.4.1) can not see the Internet as it does not have an ISP connection (unlike x.y.0.1 & x.y.8.1).
I suspect that this is a static route issue? Any suggestions on how to fix this problem will be very helpful.
Regards, Martin
I suspect your gateway is wrong. I guess it should be 192.168.0.1 ("dear 192.168.0.2, please use 192.168.0.1 as your gateway").
Hmmm.....
But without "using" 192.168.0.2, 192.168.4.1 can't reach 192.168.0.1?
So if 192.168.0.2 in not the gateway, should it be a static route?
Regards, M.
It's hard to say - what actually is 192.168.0.2? Nothing in your diagram "is" 192.168.0.2, only a reference to it being somebody's gateway.
The router that is next in line to the Internet should be the gateway. It is always a machine that is outside the router, but reachable directly from it on a wired or wireless link.
Using one of your own IPs as gateway makes no sense.
The diagram shows that the HH5A on the left with IP 192.168.0.1 is connected to an ISP and also reachable directly from the middle router 192.168.0.2. So it should be the middle router's default gateway. A request for the Internet (NTP, update download, etc) will be originated from 192.168.0.2 and sent through the left router. Of course the network on the right side could instead be used with equal results.
In addition to the gateway router's IP, you also need to set the DNS server address there. Likely again the main edge router 192.168.0.1 should be set as value, (as it is the gateway outwards and has DNS).
Sorry that I am not defining my question as well as I should. Let me add a bit more detail to my "middleman":
From where are you getting on to "middleman"? If you get on to middleman from one of its connected networks, then it does not matter if you break the default gateway, because the DG will not be in use when you're managing it. So you have more chance of being able to get the setting right.
Thank you all for your advice. Just for the record, I think I now have my "middleman" working as I would like. However, I would welcome any additional comments you may wish to make.
In graphical terms, this is it:
The step that made it all work, was to add a Default Gateway (DGW:192.168.0.1) to the "Left" WiFi Interface that connects to the barrier router. Now any request for Internet Resources (NTP, opkg, etc) are first sent to x.y.0.2. Then forwarded to x.y.0.1 then out to the web.
Setting the LAN Interface (x.y.4.1) DGW to x.y.0.2 or x.y.0.1 seems to make no difference to the traceroute output. But leaving it pointing as depicted in the curved arrows seems to make sense to me.
Regards, M
Correct, the default gateway route needs to be set on the interface which can reach the gateway directly. Any packet destined for an IP that is not one of the LANs will be sent there in the hope that that router can do something with it (usually forward it to the Internet). With conventional destination-based routing, there is only one routing table, so there can only be one usable default route.
