Posted: Wed Jun 22, 2022 0:16 Post subject: Trouble configuring secondary DD-WRT router via lan to wan
For router 1, I have xr500 dumaos set to 192.168.0.2 wan ip, subnet 255.255.255.0 and gateway as 192.168.0.1 with quad9 dns with lan ip 192.168.1.1
For router 2, I have xr500 dumaos set to 192.168.1.2 wan ip, 255.255.255.0 subnet, and 192.168.1.1 gateway with quad9 dns with lan ip 192.168.2.1
The reason I am using wan to lan instead of lan to lan is because I need nat and qos for the second router on. When I switch router 2 over from dumaos to dd-wrt and input the settings in basic setup, the same settings do not work, no internet etc.
What are the LAN ip addresses of each router? Would help if you gave us a visual presentation (screenshots) of the Setup -> Basic Setup page and applicable DumaOS page in entirety. I have a feeling there is a conflict with IP address settings... _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Posted: Wed Jun 22, 2022 4:42 Post subject: Secondary router working settings, how to convert them to DD
This is a screenshot of my router 2's working static wan ip settings, along with the configured lan ip of 192.168.2.1 that doesn't bother 192.168.1.1 aka router 1s lan ip. These settings work perfectly as a secondary router, but if I try to input the same settings in the ddwrt basic setup page I will get no connection. I flip between the latest firmwares and kong build 9/23/2018
Did you perhaps change the Operating Mode from Gateway (the default) to Router on the second router?
I may have tried that before but I don't remember restarting after switching it if that would of made a difference.
Router mode disables NAT. As such, it requires that the first router has a static route pointing to the WAN ip of the second router as the gateway to to the second router's LAN (apparently 192.168.2.0/24). Failure to do so is a common mistake.
Did you perhaps change the Operating Mode from Gateway (the default) to Router on the second router?
I may have tried that before but I don't remember restarting after switching it if that would of made a difference.
Router mode disables NAT. As such, it requires that the first router has a static route pointing to the WAN ip of the second router as the gateway to to the second router's LAN (apparently 192.168.2.0/24). Failure to do so is a common mistake.
Frankly, there's not much reason to change from Gateway to Router mode anyway. But some ppl insist on trying, and in that case the static route is mandatory.
I actually see somewhere to put static routes on my first router. I will have to fiddle with this setting. Weird that I didn't have to do this with dumaos but I will test this out.
To clarify, I see a place for host ip, netmask, gateway, metric, and interface. For host ip, I would put the wan ip of the 2nd router 192.168.1.2, the netmask is 255.255.255.0 same as the static wan ips set previously or is it 255.255.255.255? Gateway is 192.168.2.1 or 192.168.2.0? Won't allow me to add 192.168.0.1/24. And as for metric is it 1 or 2? And finally, interface lan, wan?
In this scenario, there is no reason to run NAT on the second router.
Enter this line in the Firewall script on router 1 to NAT all LAN segments out to Internet.
iptables -t nat -A POSTROUTING -o `get_wanface` -j MASQUERADE
Good point here. If you decide to use Router mode on the second router, then you will have an issue w/ router #1 since dd-wrt, by default, only NAT's its own local network over the WAN. Any additional networks (like that of router #2) will NOT be NAT'd unless you explicitly do it yourself (or as PYB suggests, just NAT everything).
That's why I try to sway users away from using Router mode. Yes, technically NAT shouldn't be necessary, but the reality is, less experienced users end up getting into trouble because they fail to properly configure daisy-chained routers using Router mode. Gateway mode (the default) just simplifies matters.
The problem is that Router 1 is still running DumaOS, not DD-WRT (re-read the OP carefully); however, that is a very good point, otherwise. The *other* problem here is the XR500 is Atheros, not Broadcom so the mods should move this topic... _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Thanks for this little explanation. I now have converted my second Netgear router(8500) to ddwrt. 1st router R9000...2nd R8500 both working smoothly on latest ddwrt firmware.