NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas Remote Using Public RIPE IP Address
The reason I'm here is because of unstable connections to my readynas via Readynas Remote.
After a little reading I find that the 5.x.x.x IP address is a public address assigned to RIPE. I believe that is the reason I am having connection issues when trying to use Readynas Remote.
I've read that "They've [Netgear] had around 2 1/2 years to fix this (the 5.x.x.x addresses were allocated to RIPE in Nov 2010)."
I can access the Readynas locally, but currently when I try remote access it's not working; sometimes it works sometimes it doesn't. The router and internet connection the readynas is connected to is stable and online. I'm using a Pro 2.
Is there a way I can stop the Readynas from using this public IP assigned to RIPE and get my remote connection more stable???
Thanks for the help.
After a little reading I find that the 5.x.x.x IP address is a public address assigned to RIPE. I believe that is the reason I am having connection issues when trying to use Readynas Remote.
I've read that "They've [Netgear] had around 2 1/2 years to fix this (the 5.x.x.x addresses were allocated to RIPE in Nov 2010)."
I can access the Readynas locally, but currently when I try remote access it's not working; sometimes it works sometimes it doesn't. The router and internet connection the readynas is connected to is stable and online. I'm using a Pro 2.
Is there a way I can stop the Readynas from using this public IP assigned to RIPE and get my remote connection more stable???
Thanks for the help.
4 Replies
Replies have been turned off for this discussion
- Netgear should stop using the address range, but I don't think that is causing your connection issues via Remote. I think that is unreliability in the netgear cloud.
The main failure mode is that a system with the ReadyNAS remote client installed cannot reach the true 5.x.x.x addresses, because the remote VPN client will route traffic to those addresses to the the netgear servers instead. - Ya, I saw this issue awhile ago with real Internet servers in 5.x address space. Remote becomes useless then, as it blocks all that traffic.
I use n2n (http://www.ntop.org/products/n2n/) now. Manual setup at first, but acts similar. Uses a 'supernode' like peerserver.netgear.com broker server. Then each 'edge' client uses that for initial connection, before going p2p to each host it wants to talk to. Added benefit of being actually stable, and lets me use my own true private IP ranges.
I like the concept, though it would be more powerful if they had the software running on mobile devices too. Are you using the NAS as the supernode?chirpa wrote: Ya, I saw this issue awhile ago with real Internet servers in 5.x address space. Remote becomes useless then, as it blocks all that traffic.
I use n2n (http://www.ntop.org/products/n2n/) now. Manual setup at first, but acts similar. Uses a 'supernode' like peerserver.netgear.com broker server. Then each 'edge' client uses that for initial connection, before going p2p to each host it wants to talk to. Added benefit of being actually stable, and lets me use my own true private IP ranges.- I went with another system, more stable, as supernode.
There is also this dandy VPN server: http://www.softether.org
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
