NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Static routes with WNR3500Lv2
I'm having a problem with devices on a non local (192.168.0.x) subnet reaching the Internet via the WNR3500Lv2. The Firmware Version is V1.2.0.34_40.0.75. My configuration is a follows. First, I don'...
TheEther I finally have a solution for my issue. I loaded "Tomato v1.28.0000 MIPSR2-132 K26 USB AIO" firmware and everything I need now seems to work fine. Nice piece of software. Lots of features over the stock Netgear firmware. I like that it's linux based and you can ssh to manage it.
I did hear back from engineering. The capability to NAT/route non-local subnet traffic was specifically removed. They were concerned that requests for features (port forwarding, DoS protection, etc.) for stuff that was non-local would complicate things for a configuration that few people had. Maybe it's a Broadcom chip issue. We'll see. I'll do some testing.
Thanks for your help on this issue.
Thanks for your help.
"I suspect the problem is that the WNR3500Lv2 is not performing NAT on traffic from the 192.168.0.0/24 subnet. You say that things worked with your WGR614v9. Were you using the same subnets (i.e. 10.120.102.0/24 and 192.168.0.0/24)?"
This is my suspicion (not performing NAT correctly on the 192.168.0.0/24 subnet traffic) as well. Just to verify, I re-installed my old WGR614v9 router with the same configuration (i.e. 10.120.102.0/24 and 192.168.0.0/24 subnets) and it does work correctly. I'd try your suggestion of using a more specific subnet of 10.120.102.0/24 but this subnet contains a cluster of openstack servers and reconfiguring would be a challenge. I'll check with tech support tomorrow. This has to be a bug. I don't know why you would support static routes and not NAT the traffic from those networks especially since it was supported in older products. Hopefully they will have a solution.
I would appreciate a follow-up once you hear from Netgear. I'm curious whether they deliberately removed this functionality or if it's a bug.
Stay tuned. I am getting the run around from tech support. I'm now told I need a ProSAFE business class router to get the functionality I had in my old WGR614v9. Just finished a chat with ProSAFE pre-sales. They said the FVS318G V2 should NAT non-local IP subnet traffic to the WAN port. I'll buy a FVS318G V2 and see. Will update this thread when I have an answer.
It's too bad they won't give you a straight answer about NAT support on the WNR3500Lv2 or any consumer-grade Netgear router. Perhaps a moderator can check directly with Engineering. Specifically, the question is, will the current generation of consumer-grade Netgear routers perform NAT on other local subnets besides the directly attached subnet? In other words, will traffic from subnet B going to the Internet be NAT'd?
Internet-----Netgear router------Subnet A-------Another Router--------Subnet B
I've asked that very question many times in my conversations and can't get a straight answer. So I upgraded to a FVS318Gv2 and still no joy. Interestingly it gets a little further than the WNR3500Lv2 in some traffic reaches the internet. I can:
- Do a nslookup and get a reposne fron the internet.
- Ping a device on the Internet if I use an IP address vs. a DNS name
- Sometimes I can ping a device on the Internet using a DNS name
- Traceroute successfully
- I can get half of a FTP connection. I can connect using the control channel, but can't do data transfers
But,
- can't ssh or scp to devices on the internet
- can't connect using http
- can't apt-get
I spoke with tech support at length but they can't figure out why it's not working. I can't even get them to say "it should work" but there appears to be a problem. Basically tech support is useless.
I needed to go back to my WGR614v9 router to get any work done.
TheEther I finally have a solution for my issue. I loaded "Tomato v1.28.0000 MIPSR2-132 K26 USB AIO" firmware and everything I need now seems to work fine. Nice piece of software. Lots of features over the stock Netgear firmware. I like that it's linux based and you can ssh to manage it.
I did hear back from engineering. The capability to NAT/route non-local subnet traffic was specifically removed. They were concerned that requests for features (port forwarding, DoS protection, etc.) for stuff that was non-local would complicate things for a configuration that few people had. Maybe it's a Broadcom chip issue. We'll see. I'll do some testing.
Thanks for your help on this issue.