Hello folks
I am not currently running Merlin firmware on my ASUS RT-N66U, but my question is would running it solve my issue below. Thanks!
The RT-N66U has a LAN network of 192.168.0.1. There is a router on the network at 192.168.0.179 that links to the 192.168.1.0 network. I have entered a static route on the RT-N66U to direct 192.168.1.0 traffic to 192.168.0.179.
If I ping from the 192.168.0.1 to the 192.168.1.0 net, all is good. But if I ping from the 192.168.1.0 net to 192.168.0.103 ,for example, it gets dropped by the router.
I ran a trace and saw that the pings are reaching the client at 192.168.0.103 and there is a response but it is dropped at the RT-N66U.
If i add a static route on the 0.103 client and point directly to 192.168.0.179 all is ok.
I need the RT-N66U to forward traffic that does not originate on its LAN as I am not able to add static routes to all devices. Will this be solved by Merlin software or a modification to the iptables?
Thanks!!
I am not currently running Merlin firmware on my ASUS RT-N66U, but my question is would running it solve my issue below. Thanks!
The RT-N66U has a LAN network of 192.168.0.1. There is a router on the network at 192.168.0.179 that links to the 192.168.1.0 network. I have entered a static route on the RT-N66U to direct 192.168.1.0 traffic to 192.168.0.179.
If I ping from the 192.168.0.1 to the 192.168.1.0 net, all is good. But if I ping from the 192.168.1.0 net to 192.168.0.103 ,for example, it gets dropped by the router.
I ran a trace and saw that the pings are reaching the client at 192.168.0.103 and there is a response but it is dropped at the RT-N66U.
If i add a static route on the 0.103 client and point directly to 192.168.0.179 all is ok.
I need the RT-N66U to forward traffic that does not originate on its LAN as I am not able to add static routes to all devices. Will this be solved by Merlin software or a modification to the iptables?
Thanks!!