NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Setting up a ReadyNAS 214
Hi, I have a new ReadyNAS 214 which I intend to use on a Mac network to stream iTunes and contain personal data. I am totally confused by the AFP, SMB, etc settings and wonder which I should set. In m...
Just pick LACP with layer-2 hashing. FWIW, that is what the R8500 is using. That gives the most predictable results (not always the best performance, just the most repeatable performance).
Here's the way it works: The hashing is used by the NAS to decide which NIC card will send each data flow. It's basically like a coin-flip. So each data flow from the NAS to device X will always use only one NIC. Also, since this is an xmit decision, the router also is making this decision, and it could choose a different NIC for the return traffic.
Layer 2 uses the mac addresses of the NAS and the receiving device (which are hard-wired into the ethernet chips, and always are the same). Layer 3 adds in the IP addresses (which will vary if you use DHCP). Layer 3+4 adds in the TCP/UDP ports being used. That normally is only used if you are also using bonding in the receiving device.
There are a couple of implications.
One is that every data flow through the bond is limited to 1 gigabit. That's because every flow uses just one NIC in the bond. That is by design - the assumption is that the clients aren't using a bonded connection, and you don't want to overrun their 1 gigabit connection.
Second, if you sending from the NAS to 2 devices there is a 50-50 chance that the NAS will use the same NIC for their xmit traffic. If you look at both directions, there's a 75% chance that either the xmit or the receive traffic will share a NIC. So the bond is often underutilitized if you only have a couple of devices.
Since the different hashes give different answers to the "coin flip" you can sometimes get a better NIC allocation with a different hash. That can improve throughput with specific devices (when you only have a couple).
But as far as streaming performance goes, it really doesn't matter much. Streaming doesn't use as much bandwidth as most people think. Even full 1080p BluRay has a max of 54 mbits (8 megabytes per second). Even without bonding, that's only about 5% of the link capacity. And most HD streams aren't full BluRay - they are in the 1-2 megabytes per second range. So the hash isn't something you need to over-think.
Herbert323 wrote:
Thanks for the quick answer. Actually Plex is now supported on the Apple TV4. They even have an app for it.
my router is a Humax from my internet provider but I have a Netgear R8500 connected as well.
Herbert
With the R8500, go to the advanced tab, and look in Setup->Lan Setup. You enter the mac address of the NAS and the IP address you want to assign it there.
You can see the mac address (and the current IP address) on Administration->attached devices. You can select and copy the mac address (easier than typing it in). I suggest assigning the current IP address of the NAS.
Your R8500 also supports LACP link aggregation, so you can easily set that up when you get to it. There are 2 LAN ports on the router that you need to use. I I tested it with my RN202, and it works fine. Though normally you won't notice any speed increase.
Stephen,
Thank you for your very easy to understand response. Worked out well. One more question if I may, what setting should I use for link aggregation? I am confused by all the different hashes and choices offered. My Mai. Purpose again is not so much speed as streaming video.
Herbert
Just pick LACP with layer-2 hashing. FWIW, that is what the R8500 is using. That gives the most predictable results (not always the best performance, just the most repeatable performance).
Here's the way it works: The hashing is used by the NAS to decide which NIC card will send each data flow. It's basically like a coin-flip. So each data flow from the NAS to device X will always use only one NIC. Also, since this is an xmit decision, the router also is making this decision, and it could choose a different NIC for the return traffic.
Layer 2 uses the mac addresses of the NAS and the receiving device (which are hard-wired into the ethernet chips, and always are the same). Layer 3 adds in the IP addresses (which will vary if you use DHCP). Layer 3+4 adds in the TCP/UDP ports being used. That normally is only used if you are also using bonding in the receiving device.
There are a couple of implications.
One is that every data flow through the bond is limited to 1 gigabit. That's because every flow uses just one NIC in the bond. That is by design - the assumption is that the clients aren't using a bonded connection, and you don't want to overrun their 1 gigabit connection.
Second, if you sending from the NAS to 2 devices there is a 50-50 chance that the NAS will use the same NIC for their xmit traffic. If you look at both directions, there's a 75% chance that either the xmit or the receive traffic will share a NIC. So the bond is often underutilitized if you only have a couple of devices.
Since the different hashes give different answers to the "coin flip" you can sometimes get a better NIC allocation with a different hash. That can improve throughput with specific devices (when you only have a couple).
But as far as streaming performance goes, it really doesn't matter much. Streaming doesn't use as much bandwidth as most people think. Even full 1080p BluRay has a max of 54 mbits (8 megabytes per second). Even without bonding, that's only about 5% of the link capacity. And most HD streams aren't full BluRay - they are in the 1-2 megabytes per second range. So the hash isn't something you need to over-think.
Thank you very much. That worked.
i am truly impressed with the ReadyNAS 214 in combination with the R8500. My WIFI and download speeds are fantastic.
Herbert
Herbert323 wrote:
Thank you very much. That worked.
i am truly impressed with the ReadyNAS 214 in combination with the R8500. My WIFI and download speeds are fantastic.
Herbert
I'm glad you are up and running. The R8500 is a very nice wave-2 ac router, and of course just launched as Netgear's top-of-the-line home router. FWIW, I find that the 5ghz-1 radio gives the best speeds (somewhat better than 5ghz-2). Though 5ghz-2 is also fast.
If you haven't upgraded to 6.4.0 yet, I suggest holding off until 6.4.1 is released. The other option is to go directly to 6.4.1 beta (which is available in the forum).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
