NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Unable to ping external server
Hello,
I have a RN 516 running firmware 6.2.4.
I've been trying to setup Bittorrent Sync on the RN, and it's working. But, I've been trying to use the option to setup predefined hosts.
This sets up a direct connection from my server on the internet to my RN via IP addresses. I've setup port forwarding on my router to allow the incoming port to be routed to the RN.
I've not been able to get this to work, and while in SSH on the RN, I decided to try pinging the IP of my linux server on the internet, but it doesn't go thru. I am able to ping other known IP addresses without any issues, and I can ping my server from my macbook without issue. The macbook and readynas are all on the same network. Only pinging the server from the readynas it doesn't seem to go thru, 100% packet loss.
Is there a firewall or something on the RN that would cause the ping not to go thru? Is there a way to do a trace route or something similar on the RN to test where the failure is?
Thanks.
I have a RN 516 running firmware 6.2.4.
I've been trying to setup Bittorrent Sync on the RN, and it's working. But, I've been trying to use the option to setup predefined hosts.
This sets up a direct connection from my server on the internet to my RN via IP addresses. I've setup port forwarding on my router to allow the incoming port to be routed to the RN.
I've not been able to get this to work, and while in SSH on the RN, I decided to try pinging the IP of my linux server on the internet, but it doesn't go thru. I am able to ping other known IP addresses without any issues, and I can ping my server from my macbook without issue. The macbook and readynas are all on the same network. Only pinging the server from the readynas it doesn't seem to go thru, 100% packet loss.
Is there a firewall or something on the RN that would cause the ping not to go thru? Is there a way to do a trace route or something similar on the RN to test where the failure is?
Thanks.
4 Replies
Replies have been turned off for this discussion
- This is because the I.P. of your server is in the 5.X.X.X range.
StephenB wrote:
Historically, the 5.x.x.x address space was originally reserved for "experimental use", so it was ok for Remote to use it when it first launched. But as IPv4 addresses ran out, IANA reclaimed as many address ranges as they could; reassigning them for general use. 5.x.x.x was reclaimed in 2010, and ended up assigned to RIPE NCC (the group that manages internet addresses in Europe and some Middle Eastern countries). But since Readycloud hijacks the entire 5.x.x.x address space, your requests are being routed to the Readycloud server through the ReadyRemote/Leaf VPN. - I turned off ReadyCloud and ReadyRemote (just in case), and was able to ping my 5.X.X.X server. Problem is now solved for me.
mdgm wrote: This is because the I.P. of your server is in the 5.X.X.X range. StephenB wrote:
Historically, the 5.x.x.x address space was originally reserved for "experimental use", so it was ok for Remote to use it when it first launched. But as IPv4 addresses ran out, IANA reclaimed as many address ranges as they could; reassigning them for general use. 5.x.x.x was reclaimed in 2010, and ended up assigned to RIPE NCC (the group that manages internet addresses in Europe and some Middle Eastern countries). But since Readycloud hijacks the entire 5.x.x.x address space, your requests are being routed to the Readycloud server through the ReadyRemote/Leaf VPN.
Ok,
The 5.x.x.x thing is now at least 5 years old,
and the new ReadyCloud client seems to still missuse it...
How many more years Netgear needs to solve the issue?
(This has something to do with working products, usable software, providing upgrades as needed and finally influences the selling of ReadyNAS boxes,
as the situation is now, we won't sell any readynas boxes when remote access is needed)
BTW: Experimental does not mean "regular use", so you did either use it wrong, or your software is also experimental...- I agree that a fix is long overdue.
Here I think you are misunderstanding. Netgear has never actually used the 5.x.x.x address space for routing over the internet. What they did was somewhat different - they built a private (tunneled) VPN using that address space. The consequence is that they have blocked access to that space on machines with Remote installed, but from a routing perspective they have never used the addresses for internet traffic.aschild wrote: BTW: Experimental does not mean "regular use", so you did either use it wrong, or your software is also experimental...
There were some practical reasons for doing what they did (they had to chose some address space, and 192.168.x.x or 10.x.x.x would have both created some messy problems to solve). At the time it was expedient and seemed safe enough. Maybe providing a IPv6 version of remote is one way out of the box they are in now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
