NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Default route on ReadyNAS 4220
Hello there, I am trying to set a default route using statically configured eth1 interface. I am in Networks - Routes menu and I enter 0.0.0.0 for IP and 0.0.0.0 for subnet mask. Subnet mask does not...
until I have physical access to the box, this is my temprary solution. Apperatnly though it will not work if the ReadyNAS is rebooted
root@Netgear:/# route delete default gw 0.0.0.0 eth0
root@Netgear:/# route add default gw 192.168.100.1 eth1
Here is the definition of Default Route:
In computer networking, the default route is a setting on a computer that defines the packet forwarding rule to use when no specific route can be determined for a given Internet Protocol (IP) destination address. All packets for destinations not established in the routing table are sent via the default route.
Given this...how do you set default route in ReadyNAS to connect to, for example, Amazon Cloud Storage server with IP of 54.122.77.83
pstoev wrote:
Given this...how do you set default route in ReadyNAS to connect to, for example, Amazon Cloud Storage server with IP of 54.122.77.83
I think your also confusing a default route with a VPN.
The answer to your question directly is to set your ETH1 DEFAULT GATEWAY to 192.168.100.1
192.168.100.1 you stated as being the gateway out to the internet.
TeknoJnky No VPN ...public open server...just any public IP on the internet, I am only using it as an example to explain that even having ETH1 DEFAULT GATEWAY to 192.168.100.1 ReadyNAS does not go out to Internet for anything through ETH1. not for DNS, not for NTP, not for PING. It appears it thinks that ETH0's "owns" the default route, as per the route table previously posted. I was hoping that setting a default route 0/0 with gateway 192.168.100.1 will change that behaviour.
pstoev wrote:
TeknoJnky No VPN ...public open server...just any public IP on the internet, I am only using it as an example to explain that even having ETH1 DEFAULT GATEWAY to 192.168.100.1 ReadyNAS does not go out to Internet for anything through ETH1. not for DNS, not for NTP, not for PING. It appears it thinks that ETH0's "owns" the default route, as per the route table previously posted. I was hoping that setting a default route 0/0 with gateway 192.168.100.1 will change that behaviour.
ETH0 should not have a gateway, or you can possibly try putting 192.168.100.1 in ETH0 default gateway section.
I do not know if the readynas prioritizes ETH0 over ETH1 default gateways. If so, then really the main solution is to put the INTERNET subnet on ETH0.
In other words switch the network settings for ETH0 and ETH1 then switch cables.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
