DSM-G600, DNS-3xx and NSA-220 Hack Forum

/ # curl http://portcheck.transmissionbt.com/5141
curl: (6) Couldn't resolve host 'portcheck.transmissionbt.com'
/ # curl -o engadget.html http://www.engadget.com

curl: (6) Couldn't resolve host 'www.engadget.com'
/ # wget http://www.inreto.de/dns323/fun-plug/0.5/packages/uclibc-0.9.29-7.tgz
wget: bad address 'www.inreto.de'
/ #

Most likely you're right, but why? And most importantly, how to fix it.

I would assume this was most likely a DNS error, i.e. the NAS either had no DNS server setting to begin with (normally this information is exchanged when the device connects to your router and requests an IP via DHCP), or the DNS server was offline.

If you manually assign a a static IP address to the NAS make sure that the DNS server is set as well.

What is the path to the download directory? Does it have enough space on that volume?

KyleK wrote:

I would assume this was most likely a DNS error, i.e. the NAS either had no DNS server setting to begin with (normally this information is exchanged when the device connects to your router and requests an IP via DHCP), or the DNS server was offline.

If you manually assign a a static IP address to the NAS make sure that the DNS server is set as well.

Thank you sir...

This was my issue as well. I have OpenDNS set to block sites I don't want my kids to see (At the router level). DHCP was passing this on hence the problem.

Static ip and New DNS resolved the problem.

Thanks again.

Additionally, just saw that a new version of curl: Updated to 7.21.7 was posted. Any reason to update?

Check with the following commands if Transmission is downloading data to the correct folder:

$ transmission-remote -si
$ transmission-remote -t <torrentID> -i

The first command gives you session information, including the default download folder
The second command shows status information for a specific torrent, including its download folder.

See if these folders actually exist. Anything pointing to /home/root or some such will fill up really fast because that's the built-in RAM drive.

Are you using the watch folder functionality of Transmission?
If so, try and chose a watch folder different from the one where Transmission is downloading to.

The changes between Transmission 2.32 and 2.33 are solely related to MacOS X Lion compatibility and have no influence whatsoever on the NAS version of Transmission. I therefore chose to not make a package of 2.33.

Transmission 2.40 is coming soon anyways.

KyleK wrote:

The changes between Transmission 2.32 and 2.33 are solely related to MacOS X Lion compatibility and have no influence whatsoever on the NAS version of Transmission. I therefore chose to not make a package of 2.33.

Transmission 2.40 is coming soon anyways.

thanks ofr the answer.My problem is a rule on a private tracker that required the last version of transmission ,so i must upgrade to 2.33

There you go. Transmission v2.33 is now available from the first post.

Enjoy

Note to everyone else: Except for Transmissions PeerID (with which it authenticates itself to trackers), there is no code change between 2.32 and 2.33. So unless any of your trackers require you to use the very latest version of Transmission, you do not need to upgrade.

T 2.40 won't be too long, I guess.

hello all,

wanted to download the newest version on transmission for ch3mnas but seems that the link is broken and don't seem to find any other locations
can anyone help?

(location I tried is: http://kylek.is-a-geek.org:31337/files/ … 2.33-1.tgz )

thanks

strange, doesn't work here
tried via browser, wget, other pc but no luck
checked my router, disabled firewall

any other ideas?

I set up Transmission 2.33 on my DNS-323 via the instructions in this thread (thanks!) and moved over a bunch of torrents from my Mac, (running Transmission 2.40b1.)

Most everything's working fine. However, completed torrents with filenames that include UTF-8 characters (like é and ñ and ：) are not showing up as completed: files with such characters show up as 0 Bytes, and the files immediately preceding and following those show as only partially complete, (though the full files are there.) If the top-level directory of the torrent has a UTF-8 character, the whole torrent shows up as 0 Bytes.

My DNS-323 has firmware version 1.10 (beta from 04/06/2011.)

Since seeing these issues I have re-formatted the NAS drives (RAID-1,) to ensure Unicode support. First formatted as ext3, and then -- (encountering some strange issues where folders with UTF-8 characters would repeatedly appear and disappear when viewing the drive from the Mac, and reading that DNS-323's ext3 support is spotty,) -- as ext2.

I can see the UTF-8 filenames just fine through SMB Mac filesharing and in my terminal via SSH.

Any ideas why Transmission doesn't like these files, and what I can do to fix this?

andrew5368: Can you reproduce the crash reliably? Do you know if it happens because of a specific torrent?
Unfortunately the daemon binary is stripped, so a generated core file won't help us here.
If necessary I can provide a build that is not stripped.