[SOLVED] ReadyNAS with a spare eth1

Habitual · 06-05-2014, 09:07 PM

Client bought a ReadyNAS 102 when his server ran out of disk space.
I got the device mounted at /mnt/bigdata and configured for fstab.

The client wants to keep the ReadyNAS 'traffic' off his eth0:x network.

There's an unconfigured eth1 I'd like to use and I have some questions about that.

If I configure eth1 to use 192.168.0.2 using

Code:

ifconfig eth1 192.168.0.2 netmask 255.255.255.0

will it matter if there's no gateway, and the device will never talk to the outside world and only be used as a mount for the extra storage?

rsync of 1.1T is going to take 10 more hours, so if you need any more info, fire away.

CentOS release 6.4 (Final) (I "know")

iscsi-initiator-utils-6.2.0.873-10.el6.x86_64

Code:

ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:25:90:83:97:0a brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:25:90:83:97:0b brd ff:ff:ff:ff:ff:ff

ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:25:90:83:97:0B  
          inet6 addr: fe80::225:90ff:fe83:970b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11896 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1261254 (1.2 MiB)  TX bytes:468 (468.0 b)
          Memory:feae0000-feb00000 

route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
209.112.245.0   *               255.255.255.0   U     0      0        0 eth0
67.207.212.0    *               255.255.255.0   U     0      0        0 eth0
216.105.34.0    *               255.255.255.0   U     0      0        0 eth0
link-local      *               255.255.0.0     U     1002   0        0 eth0
link-local      *               255.255.0.0     U     1003   0        0 eth1
default         lwdc.ar07.fa1-7 0.0.0.0         UG    0      0        0 eth0

Thanks!

Emerson · 06-05-2014, 09:20 PM

Just make sure it is not on same subnet with eth0 and you will be OK.

GaWdLy · 06-05-2014, 09:34 PM

There's no need for a gateway if your traffic is staying local.

Habitual · 06-06-2014, 08:09 AM

Quote:

Originally Posted by Emerson

Just make sure it is not on same subnet with eth0 and you will be OK.

20 years in IT and I'm ashamed to say, that I don't have any subnetting.fu.

How do I make sure it's not on the same subnet?

Looks like

Code:

ifconfig eth1 192.168.0.2 netmask 255.255.255.192

should do the trick?

Thanks both of you for your time.

Emerson · 06-06-2014, 06:15 PM

Say, your eth0 is 192.168.0.X with mask 255.255.255.0.
Assign 192.168.1.X mask 255.255.255.0 to your eth1 and it will not interfere with your eth0 connection. 192.168.1.Y for your NAS and that's it.

Habitual · 06-07-2014, 07:54 AM

Emerson:
eth0 has only a public IP on 67.207.212.0/24

Somehow, the ReadyNAS is using IPv6 says the client.
I didn't do anything to cause that. He's impressed but I am confused, if that's true.

Thanks!