- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
How to set gateway of last resort in this WNDR3700.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Please tell me how to setup gateway of last resort in static
routes in WNDR3700.
I am using a Netgear WNDR3700 router (R0) as follows.
R0 L0 R1 ISP
<---------->
<------------> <---------------->
192.168.3.0 192.168.1.0
List of IP addresses.
L0 is a linux box with 2 interfaces viz.
wlan1: 192.168.1.3 (wireless)
eth0: 192.168.3.2 (wired)
The IP addresses of both interfaces of L0 have been reserved in the dhcp settings of the
routers R0 and R1
R0 (netgear wndr3700). 192.168.3.1
R1 192.168.1.1
Both R0 and R1 both have wifi and dhcp enabled.
Static routes have been setup and connectivity
is established between all the routers in the network.
Pings go in both directions between hosts in both the 192.68.3.0 and 192.168.1.0 networks.
Internet access is available in both L0 and the 192.168.1.0 network.
There is however no internet access in 192.168.3.0 network.
I think the problem can be solved by setting a gateway of
last resort in R0. Please tell me how to achieve this.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You probably need to add two static routes: a 0/0 route on R0 pointing to L0 and another 0/0 route on L0 pointing to R1. But traffic from devices on the 192.168.3.0 subnet is going to take an inefficient path through R0 to get to either the Internet or subnet 192.168.1.0, so I would not recommend doing this.
What you really want is for R0 to advertise 192.168.3.2 as the default gateway in DHCP. This way, devices on that subnet will send traffic directly to L0. L0 would still need a static 0/0 route pointing to R1. Unfortunately, the WNDR3700 can only advertise itself as the default gateway, so this is not an option.
Here are some options for you to consider.
Option 1: Swap R0 and L0
Set up R0 as an Access Point and wire it into R1 via a LAN port. Disable the DHCP server. This eliminates the 192.168.3.0 subnet. Everything would see R1 as the default gateway. I suspect that this not an option for you because R0 is probably positioned where it is to provide Wi-Fi coverage, or you are using L0 as a firewall and it has better capabilities than R0, or you can't/won't run Ethernet to R1.
Option 2: Replace L0 with a switch
Install a switch where L0 is located and wire it R1. Same considerations as option 1 except that this option allows you to keep the physical location of R0 unchanged.
Option 3: Use L0 as a DHCP server
Disable the DHCP server on R0 and enable it on L0 for the 192.168.3.0 subnet. Devices on that subnet will then send traffic to L0. L0 still needs a default route pointing to R1, but it should get that automatically via DHCP. If you are not a techie, setting up a DHCP server on Linux may be hard. dnsmasq is the standard option.
Option 4: Set up bridging on L0
The idea is to bridge the two interfaces on L0. This eliminates the 192.168.3.0 subnet, so disable DHCP on R0. This may be challenging to set up.
Option 5: Replace L0 with a range extender
Same as option 4 really but with less fuss.
Option 6: Install DD-WRT on R0
DD-WRT can easily advertise L0 as the default gateway in DHCP. This is probably just as difficult as setting up a DHCP server.
Option 7: Use static IP addressing on subnet 192.168.3.0
With static IPs you can easily set the default gateway on all devices to point to L0. Obviously, this is very cumbersome so I only mention it for completeness.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You probably need to add two static routes: a 0/0 route on R0 pointing to L0 and another 0/0 route on L0 pointing to R1. But traffic from devices on the 192.168.3.0 subnet is going to take an inefficient path through R0 to get to either the Internet or subnet 192.168.1.0, so I would not recommend doing this.
What you really want is for R0 to advertise 192.168.3.2 as the default gateway in DHCP. This way, devices on that subnet will send traffic directly to L0. L0 would still need a static 0/0 route pointing to R1. Unfortunately, the WNDR3700 can only advertise itself as the default gateway, so this is not an option.
Here are some options for you to consider.
Option 1: Swap R0 and L0
Set up R0 as an Access Point and wire it into R1 via a LAN port. Disable the DHCP server. This eliminates the 192.168.3.0 subnet. Everything would see R1 as the default gateway. I suspect that this not an option for you because R0 is probably positioned where it is to provide Wi-Fi coverage, or you are using L0 as a firewall and it has better capabilities than R0, or you can't/won't run Ethernet to R1.
Option 2: Replace L0 with a switch
Install a switch where L0 is located and wire it R1. Same considerations as option 1 except that this option allows you to keep the physical location of R0 unchanged.
Option 3: Use L0 as a DHCP server
Disable the DHCP server on R0 and enable it on L0 for the 192.168.3.0 subnet. Devices on that subnet will then send traffic to L0. L0 still needs a default route pointing to R1, but it should get that automatically via DHCP. If you are not a techie, setting up a DHCP server on Linux may be hard. dnsmasq is the standard option.
Option 4: Set up bridging on L0
The idea is to bridge the two interfaces on L0. This eliminates the 192.168.3.0 subnet, so disable DHCP on R0. This may be challenging to set up.
Option 5: Replace L0 with a range extender
Same as option 4 really but with less fuss.
Option 6: Install DD-WRT on R0
DD-WRT can easily advertise L0 as the default gateway in DHCP. This is probably just as difficult as setting up a DHCP server.
Option 7: Use static IP addressing on subnet 192.168.3.0
With static IPs you can easily set the default gateway on all devices to point to L0. Obviously, this is very cumbersome so I only mention it for completeness.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: How to set gateway of last resort in this WNDR3700.
I followed Option 3, enabling dnsmasq on L0 and it worked with the configuration I had in mind. Internet access works on all the clients connecting to 192.168.3.0 network.
Thank you so much, TheEther for your prompt and exhaustive solution.
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more