Pinging from ReadyNAS Duo

I figured this would be a very simple issue. Can't anyone answer this? :roll:

What ReadyNAS model do you have?

What version of Transmission?

ReadyNAS Duo
RAIDiator 4.1.7 [1.00a043]
Transmission 2.22

Update the firmware and update to a newer version of Transmission.

Did both a long time ago and had nothing but problems with Transmission. Went back to these older versions for a good reason, and it's been stable ever since.

How does your recommendation answer my question?

I suspected you could be encountering an issue as a result of staying on an old version of software while others move to newer versions of software.

Have you tried rebooting the NAS?

How is the I.P. set on the NAS? Is it set to automatically receive an I.P. address or is it static? If the latter have you checked to see that the DNS and Gateway settings are correct?

Can you email me your logs?: http://readynas.com/kb/faq/misc/how_do_i_send_all_logs

If you want to ping from the NAS you could install EnableRootSSH and SSH in as 'root' (no quotes - password initially set to be the same as that for the admin user) using PuTTy on Windows or the Terminal on Mac/Linux.

I discovered by disabling ReadyNAS Remote that it was the culprit and apparently causing a conflict with Transmission. So that problem is isolated but not resolved.

Thanks for the recommendation on EnableRootSSH. Being a Mac user I'm not at all competent with command line stuff (big mystery to me). There isn't another app I can install with a simple intuitive GUI that will do what I need?

I can't remember any, but then I my be mistaken.

You should be able to find all the information you need to tell things are configured correctly by downloading the logs and/or the config backup and/or looking in the config directory for the add-on.

Sushiboy wrote:
I discovered by disabling ReadyNAS Remote that it was the culprit and apparently causing a conflict with Transmission. So that problem is isolated but not resolved.

If the trackers or the peers you are connecting with use 5.x.x.x addresses, there is an IP address conflict - since remote hijacks the 5.x.x.x address space.

If that is the cause, there is no workaround other than disabling remote.

There are indeed interfaces that let you ping from GUI (webmin for example can do that I think), but they will require command lines to be installed on ReadyNAS, so you are back to start.

Linux commands and OS X commands are really similar because they both use bash as a core. the command to ping is just "ping IP(or name)" for example "ping 127.0.0.1", use ctrl+C to stop pinging. If you can't ping a traceroute command can be useful. If your tracker uses a DNS name (e.g not an IP address), then you want to try the "nslookup tracker-website-name" command to see if the DNS can actually translate the name into IP.
You can try on OS X in the terminal. If you want to issue them on the NAS you would have to use "ssh root@NAS-IP" in the terminal then issuing the ping / traceroute / nslookup command