Forum Discussion

Tutor

May 09, 2018

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...

Installation & Upgrade

pstoev
May 10, 2018
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

StephenB

Guru - Experienced User

May 10, 2018

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?

pstoev

Tutor

May 10, 2018

Ok here is the background:

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

root@Netgear:/home/admin# netstat -nr
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window irtt Iface
0.0.0.0         172.30.1.1      0.0.0.0         UG        0 0          0 eth0
8.8.8.8         172.30.1.1      255.255.255.255 UGH       0 0          0 eth0
172.30.1.0      0.0.0.0         255.255.255.0   U         0 0          0 eth0
172.30.1.1      0.0.0.0         255.255.255.255 UH        0 0          0 eth0
192.168.99.0    192.168.199.1   255.255.255.0   UG        0 0          0 eth2
192.168.100.0   0.0.0.0         255.255.255.0   U         0 0          0 eth1
192.168.100.1   0.0.0.0         255.255.255.255 UH        0 0          0 eth1
192.168.199.0   0.0.0.0         255.255.255.0   U         0 0          0 eth2

TeknoJnky
Hero
May 10, 2018
pstoev wrote:

Ok here is the background:

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.

example static route: 192.168.99.0 255.255.255.0 > gateway 192.168.199.1 > adapter eth2

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.
- pstoev
  Tutor
  May 10, 2018
  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
  - TeknoJnky
    Hero
    May 10, 2018
    can you confirm or did you try setting ETH0 default gateway to BLANK, or alternatively to 192.168.100.1 ???
StephenB
Guru - Experienced User
May 10, 2018
pstoev wrote:

Ok here is the background:

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.