Forum Discussion

Aspirant

Mar 21, 2017

Default gateway to Internet

ReadyNas RN4220 has 6 network adapters. Each one can be connected to a different subnet. Only one subnet has a connection to the Internet. How to set the default gatewey to Internet ? ReadyNas ca...

Other Discussions

jak0lantash

Mentor

Mar 22, 2017

For a permanent solution, you should look for the correct config using the GUI. Otherwise, your modifications can potentially be overwriiten by ReadyNASd at next boot, or next write interaction with the config.

jrsmith61

Tutor

Apr 07, 2017

I have a similar problem with my RN626X and I wonder if it is related to the order in which the bonds were created. The RN626X has 2 x 1 Gb interfaces, eth0/1, and 2 x 10 Gb interfaces, eth2/3. I created bond0 using the 10 Gb interfaces and bond1 using the 1 Gb interfaces. bond0 connects to an isolated network used for iSCSI only. bond0 is configured with a router address of 0.0.0.0. bond1 connects to a network with Internet access. bond1 is configured with a router address that points to my firewall. DNS for bond1 points to the same firewall.

Everything was working fine until I installed 6.7.0 last night. After that, I could only access my ReadyNAS from networks to which it is directly connected. While searching for a solution I found this discussion. I was able to correct the problem by enabling ssh and using ip route to change the default gateway, but I don't think that is a permanent solution.

I can't figure out how to use the GUI to make the change stick. I thought I might try deleting and recreating the bonds so that bond0 uses the 1 Gb NICs and bond1 uses the 10 Gb NICs, but I'm open to suggestions.

Kris_Nalej
Aspirant
Apr 10, 2017
Yes, it's trure that after update 6.7.0 you could only access ReadyNAS from networks to which it is directly connected.
I have the same issue.
The solution is to add each subnet to 'routes' in GUI ( menu 'Network' than tab 'Routes'). It's worked for me.
Unfortunetly I have still problem to acces the Internet. :(
- jrsmith61
  Tutor
  Apr 10, 2017
  I deleted and recreated both bonds and added a static route using the command line, ip route change default via 192.168.168.1 dev bond0. The default route has been persistent across multiple reboots.