NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN516 - Won't connect to ReadyCloud since 6.9.5 update
Since I've updated to FW version 6.9.5 I can't get the ReadyCloud App on either of my Samsung S9 phones or access my device via the ReadyCloud site. I appears, but says there are no volumes, and the...
So I fixed it. I was looking for your two green check marks when I noticed it said no internet available. Somehow my port aggregation got changed from Layer 2+3 to Layer 3+4. Switched it back to Layer 2+3 and now its working again.
So I fixed it. I was looking for your two green check marks when I noticed it said no internet available. Somehow my port aggregation got changed from Layer 2+3 to Layer 3+4. Switched it back to Layer 2+3 and now its working again.
Mr_HoneyDo wrote:
Somehow my port aggregation got changed from Layer 2+3 to Layer 3+4. Switched it back to Layer 2+3 and now its working again.
The xmit hash only affects the coin-flip that determines which NIC is used to transmit each packet. It doesn't affect internet connectivity.
But changing the setting would restart the NICs, and that might have done it.
StephenB wrote:
Mr_HoneyDo wrote:
Somehow my port aggregation got changed from Layer 2+3 to Layer 3+4. Switched it back to Layer 2+3 and now its working again.
The xmit hash only affects the coin-flip that determines which NIC is used to transmit each packet. It doesn't affect internet connectivity.
But changing the setting would restart the NICs, and that might have done it.
Everything is working. Something more must be going on with the xmit hash and the Ready Cloud service because it completely resolved the issue. I had restarted, shutdown and restarted, toggled the service and even restarted my switch and nothing changed the behavior until I corrected the Layer selection. End of the day its working, but I would be curious to hear Netgear chime on what might have been going on there.
It would be interesting to know if the problem recurs if you change the hash back to layer 3+4. If it does, it'd be useful to know if the only symptom is disrupting the ReadyCloud service. If there is something broken in LACP I'd expect it to affect all services.
FWIW, layer 2+3 hashing guarantees that the total flow from the NAS to a client can't exceed the link speed of a single NIC. This guarantee can prevent packet loss if the ReadyNAS NICs are gigabit and the path from the NAS to the client is also gigabit . In other cases (for instance WiFi), the application relies on TCP congestion control (or UDP retransmission).
Layer 3+4 hashing doesn't have that guarantee, since traffic to different TCP/UDP ports can use different ReadyNAS NICs. So the NAS can attempt to send more than 1 gigabit of traffic to the client. I think that's very unlikely to trigger issues with ReadyCloud, since most ReadyCloud users don't have gigabit internet service. Those users are relying on TCP congestion control anyway.
StephenB wrote:
It would be interesting to know if the problem recurs if you change the hash back to layer 3+4. If it does, it'd be useful to know if the only symptom is disrupting the ReadyCloud service. If there is something broken in LACP I'd expect it to affect all services.
FWIW, layer 2+3 hashing guarantees that the total flow from the NAS to a client can't exceed the link speed of a single NIC. This guarantee can prevent packet loss if the ReadyNAS NICs are gigabit and the path from the NAS to the client is also gigabit . In other cases (for instance WiFi), the application relies on TCP congestion control (or UDP retransmission).
Layer 3+4 hashing doesn't have that guarantee, since traffic to different TCP/UDP ports can use different ReadyNAS NICs. So the NAS can attempt to send more than 1 gigabit of traffic to the client. I think that's very unlikely to trigger issues with ReadyCloud, since most ReadyCloud users don't have gigabit internet service. Those users are relying on TCP congestion control anyway.
Switched it back to Layers 3+4 and working just fine. So definitely was just the NICs acting up. Odd that a restart and especially a shutdown/restart wouldn't have resolved that previously.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
