@egc write up worked perfectly on the current latest build. if you want a static ip badly, you must only configure the wan ip address, gateway, and static dns 1. Set the gateway and dns 1 only not 2 or 3 to 192.168.1.1 and then set the wan ip to something that won't conflict with the 192.168.1.1 dhcp range, I used 192.168.1.2. Remember that is a wan ip, not lan. Worked like a charm.
The last thing I would like to figure out is how I can access the 192.168.2.1 secondary router gateway and its settings while connected to the 192.168.1.1 first router. This article says I need to set up a static route, I tried putting in (all settings done on the 1st router) 192.168.2.0 for the destination, 255.255.255.0 netmask, and the gateway as the wan ip of the second router with no success, even after disabling the firewall for testing on the second router. I tried accessing the gateway via its lan ip and wan ip with no dice.
The settings I previously mentioned allows me to successfully get into the routing table, if I inverse the destination or gateway, it won't even show up on the table
Destination Subnet Gateway
192.168.2.0 255.255.255.0 192.168.1.2 with 1 metric
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Sat Jun 25, 2022 6:16 Post subject:
Great to hear you are making prorgress
Fist consider setting router 2 back to automatic DHCP and deal with the WAN IP address of this router in an other way
Of course you need the WAN IP address of router 2 to be fixed to set a static route.
But it is better to accomplish this by setting a static lease on router 1 for router 2.
You need the WAN MAC address of router 2.
On router 1 you connect this MAC address to a static IP address and yes 192.168.1.2 can be a good choice if that is allowed by DumaOS, sometimes static addresses must be outside the DHCP scope sometimes within.
I assume there is list of connected IP addresses on the DumaOS where you can see router 2 connected and you can just add a static lease from the GUI
In this way you can keep track of all the IP addresses of router 1 (the WAN IP address of router 2 is an IP address of router 1).
What you have done with a static address on router 2 is not wrong but if you have a large number of static addresses it is difficult to keep track and by using static leases handed out by router 1 you have it all centralized in one point.
Now on to the connection of the networks.
You do need 2 things
1. Set a static route on router 1 to router 2 what you are doing is the right direction but I do not use DumaOS
2. Open up the firewall of router 2 for traffic of router 1