NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 dropping all static route packets
Hello, I have two routers in my network connected to one another. When I set a static route from my first router (R6400 with DD-WRT) to the second one (R7000 with stock OS), the second router (...
I fixed the issue by flashing Xwrt-vortex, a custom firmware that supports NAT from other subnets.
In the end, the culprit was the NETGEAR firmware. There were no issues in routing.
Really disappointed in NETGEAR firmware and it's support.
I won't be buying NETGEAR as my next router.
Apologies for being such a mess.
Here are screenshots of all my settings and what happens when I ping them:
Same results when I ping them from PC instead of router.
If you would need anything more, please let me know.
> [...] Or what your "my ISP's modem" might be.
Still wondering. Is it a modem or a modem+router? If the latter,
then what are its IP addresses (LAN and WAN/Internet)?
If your "my ISP's modem" is a simple modem, then I would expect the
LAN subnet of the (DD-WRT) router which is connected to it to be
"192.168.1.*", not "10.0.0.*".
In the first picture, I'm not sure what the circles and arrows are
supposed to tell me.
The second picture seems to show a reasonable route for the
"192.168.1.*" subnet.
In the third picture, I'd expect a WAN subnet mask of
"255.255.255.0", rather than the default for a "10.x.y.z" subnet
("255.0.0.0"). But that may be mostly harmless.
The fourth picture seems to show "Respond to Ping on Internet Port"
being checked.
The fifth picture seems to show a working "ping", from the DD-WRT
router to the R7000 WAN/Internet port, which I'd expect.
The sixth picture shows a failing "ping" from the DD-WRT router to
the R7000 LAN interface. I'm not sure if I'd expect that to work or
not. What happens if you connect some device to the R7000 LAN, and
"ping" it (from the DD-WRT router)?
My fear (based on the unexpected DD-WRT router subnet) is that your
"my ISP's modem" is a modem+router, and that its LAN is using the
"192.168.1.*" subnet. In that case, the DD-WRT router might think that
a message for "192.168.1.X" should go to its own WAN port, and. thus,
not to follow the (lower-priority) route which you added.
> If you would need anything more, please let me know.
> [...] WAN/Internet IP address of each router? [...]
In particular, that of the DD-WRT router (if it's not your public
address).
I am trying to repond to you since morning but as soon as I post a long post answering your questions, it gets deleted. Don't know why.
I am not really enjoying this forum script in use.
Anyways,
I think the ISP modem is just a modem because it does not show up in trace routes.
I just connect it to the R6400 and establish internet using PPPoE.
In the first picture,
10.0.0.1 is my R6400 router.
10.0.0.3 is my R7000 router's static IP to R6400.
192.168.1.1 is my R7000's local IP.
I already have a Windows machine (with all firewalls turned off) on the R7000 and when I ping it, all packets are dropped.
The WAN IP of the R6400 is the one provided by my ISP via PPPoE.
The WAN IP of the R7000 is 10.0.0.3 to connect to the R6400.
When I trace route from a computer on the R6400 (DD-WRT) network to a computer on The R7000's network, the trace stops at 10.0.0.3, meaning it's rejecting all packets at 10.0.0.3 and not letting me get through, so I think it's a firewall issue and not a routing issue?
Also, I am no expert but the ISP's modem should not come into picture as I am trying to locally send a packets from the R6400 to the R7000?