This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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 ?
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.
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?
eth0 - 172.30.1.5 IP is connected to the network to backup VMs on 172.30.1/24 network
eth1 - 192.168.100.50 is connected the network to backup VMs on 192.168.100/24 network AND 192.168.100.1 is the gateway out to internet
eth2 - 192.168.199.47 is connected the network to backup VMs on 192.168.199.24 network and 192.168.199.1 is the gateway to 192.168.99/24 network BUT NOT to internet
do you have a reference for ssh commands to set routes ? here is the current routing table
TeknoJnky - thanks for your response and I understand what you are saying...but how would the NAS get to 8.8.8.8 DNS or say 4.2.2.1 DNS without a default route ? Also how would it get to Netgear site for automated fimrware download/update without default route ? Also how may it connect to the Netgear specified NTP servcers without default route ? Default Route is needed for any internet-bound traffic from Netgear and that is what I am trying to set. When I try to set 0.0.0.0/0.0.0.0 - the ReadyNAS WebUI does not accept 0.0.0.0 as a subnet mask.
Ok, I have my nas NIC's bonded, so I can't currently see if each ETH has its own DNS server and/or gateway, but I would expect this;
go to network settings, find settings for ETH1
--- eth1 - 192.168.100.50 is connected the network to backup VMs on 192.168.100/24 network AND 192.168.100.1 is the gateway out to internet ---
ETH1 should have the gateway set to 192.168.100.1, and it should have a DNS server IP entered in the dns section.
The DNS server can either be a public (ie 8.8.8.8 or 1.1.1.1 etc) or it can be a private dns that can still resolve public ips (ie typcially the gateway can act as a dns resolver- 192.168.100.1).
hope that helps.
Also- you can have multiple dns servers, so if the gateway acts only as LOCAL dns resolver, you can add a 2nd dns for the public ip resolution.
also2- googles dns server 8.8.8.8 is neither a gateway or static route or local ip, so you will want to remove that from any other settings other than DNS on ETH1.
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
@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.
@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.
eth0 - 172.30.1.5 IP is connected to the network to backup VMs on 172.30.1/24 network
eth1 - 192.168.100.50 is connected the network to backup VMs on 192.168.100/24 network AND 192.168.100.1 is the gateway out to internet
eth2 - 192.168.199.47 is connected the network to backup VMs on 192.168.199.24 network and 192.168.199.1 is the gateway to 192.168.99/24 network BUT NOT to internet
Like I said, try removing any default gateway from ETH0 first and see if that works.
Ok, reading above, here is what I would suggest, swapping eth0 and eth1;
eth0 - 192.168.100.50 is connected the network to backup VMs on 192.168.100/24 network AND 192.168.100.1 is the gateway out to internet
eth1 - 172.30.1.5 IP is connected to the network to backup VMs on 172.30.1/24 network
eth2 - 192.168.199.47 is connected the network to backup VMs on 192.168.199.24 network and 192.168.199.1 is the gateway to 192.168.99/24 network BUT NOT to internet
SO,
ETH0 goes to 192.168.100.x and the internet (default gateway 192.168.100.1)
ETH1 goes to 172.30.1.x ONLY (default gateway BLANK)
ETH2 goes to 192.168.199.x AND has access to 192.168.99.x (via default gateway 192.168.199.1)
eth2 is a little more complicated and perhaps could use a static route, but should not be required.
I would suspect explicitly defining this static route would allow for quicker access to 192.168.99.x instead of having to flow down through eth0 then eth1, before finally finding the way out through eth2.
eth0 - 172.30.1.5 IP is connected to the network to backup VMs on 172.30.1/24 network
eth1 - 192.168.100.50 is connected the network to backup VMs on 192.168.100/24 network AND 192.168.100.1 is the gateway out to internet
eth2 - 192.168.199.47 is connected the network to backup VMs on 192.168.199.24 network and 192.168.199.1 is the gateway to 192.168.99/24 network BUT NOT to internet
Try deleting all your static routes, and then let us know what is broken.
I think all your local addressing should just work. It's conceivable that internet addressing will fail, but if it works correctly then there's no reason to set up any of these.
Yeah, Metric is configurable in windows, but I don't think it is in the GUI for os 6.
I'm sure some google-foo would determine if and howto modify NIC metric via linux. In case you were not already aware, os 6 uses debian jessie, so if researching try to find info related to that version (different versions of debian have different ways of doing things).
Metric determines exactly what order of precedence a network interface has.
for example, wifi vs ethernet. I believe windows typically attempts to determine metric by priortizing faster link speeds.
