Forum Discussion
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 accept such entry. What should I do ?
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
22 Replies
Normally you use 255.255.255.255 as the subnet mask for IP address 0.0.0.0
Also, you appear to have configured Google's public DNS server (8.8.8.8) as a static route - which of course won't work.
What are you trying to accomplish? Wouldn't it be simpler to just remove the second ethernet connection?
StephenB - thank you for the response, I will try that. But just to be preceise, using 0.0.0.0/32 is not normal. Industry standard says:
"The default route in Internet Protocol Version 4 (IPv4) is designated as the zero-address 0.0.0.0/0 in CIDR notation"
I will now remove the 8.8.8.8/32 route - i was using it to test.
I am trying to get the ReadyNAS connect to the NTP servers which are factory specified to be "time-e.netgear.com" and which would not work without DNS...which would not work without default route or local DNS server which we dont have.
I cannot just remove second ethernet connection. This is a backup NFS appliance for several networks and so it needs to be connected to these networks.
pstoev wrote:
StephenB - thank you for the response, I will try that. But just to be preceise, using 0.0.0.0/32 is not normal. Industry standard says:
"The default route in Internet Protocol Version 4 (IPv4) is designated as the zero-address 0.0.0.0/0 in CIDR notation"
Yeah, it might not work - (and could give you an unrouteable error). if you need 0.0.0.0 with a 0.0.0.0 mask, then you might need to use ssh.
But I don't still understand the purpose for entering it. Traffic that isn't sent to 192.168.100.x and isn't covered by another static route should be going to 192.168.100.1 anyway,. correct?
