I recently upgraded my Buffalo WZR-HP-G300NH2 from DD-WRT (Buffalo build) to Gargoyle 1.5.8. I also have a DLink DIR-825 running DD-WRT.
The DLink acts as a router for a separate subnet (192.168.1.x) than the Buffalo which is the primary router for the 192.168.0.x subnet. The Dlink has a WAN IP of 192.168.0.200 so that it can provide connectivity for its subnet. Under DD-WRT, I would setup a static route as follows:
Metric:1
Destination: 192.168.1.0
Subnet: 255.255.255.0
Gateway: 192.168.0.200
Interface: LAN&WLAN
After this setup, I could ping hosts on both subnets. In Gargoyle, I tried to replicate the above as follows:
Destination: 192.168.1.0/255.255.255.0
Network: LAN
Gateway: 192.168.0.200
Once I saved these settings, I tried pinging the DLink on both 192.168.0.200 and 192.168.1.1 addresses but did not succeed.I noticed that the metric for the route was set to 0, which in DD-WRT is apparently incorrect. I then tried changing the metric via the uci command line (uci set network.route1.metric=10) but that did not help either.
Any suggestions on what to do next?
[SOLVED] How to get routing between subnets working?
Moderator: Moderators
[SOLVED] How to get routing between subnets working?
Last edited by avggeek on Thu Dec 06, 2012 2:20 am, edited 1 time in total.
Re: How to get routing between subnets working?
Posting an update for the search engines.
After connecting to the DLink Web UI, I noticed that it's WAN IP was showing as 0.0.0.0, which was odd since the WAN IP should be the reserved IP in Gargoyle. I eventually realized that my DHCP range was set to go upto 192.168.0.150 and Gargoyle was not handing out the IP for the DLink as it was "out-of-range" (my guess).
I changed the IP reservation for the Dlink to 192.168.0.150 and updated the routing page as well. However, after a reboot the Dlink was still not getting a WAN IP. So I changed the WAN settings in the Dlink to be a static IP of 192.168.0.150. Once I did this, both subnets could see IP's on both sides.
TL;DR: Make sure the Gateway for the second subnet is assigned an IP within the DHCP range. If that doesn't work, set the WAN IP for the 2nd gateway to static IP matching it's IP assignment in Gargoyle.
After connecting to the DLink Web UI, I noticed that it's WAN IP was showing as 0.0.0.0, which was odd since the WAN IP should be the reserved IP in Gargoyle. I eventually realized that my DHCP range was set to go upto 192.168.0.150 and Gargoyle was not handing out the IP for the DLink as it was "out-of-range" (my guess).
I changed the IP reservation for the Dlink to 192.168.0.150 and updated the routing page as well. However, after a reboot the Dlink was still not getting a WAN IP. So I changed the WAN settings in the Dlink to be a static IP of 192.168.0.150. Once I did this, both subnets could see IP's on both sides.
TL;DR: Make sure the Gateway for the second subnet is assigned an IP within the DHCP range. If that doesn't work, set the WAN IP for the 2nd gateway to static IP matching it's IP assignment in Gargoyle.