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 ...
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 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
