Transmission 2.33 fails to connect to UDP trackers

I should probably put the question out there in a different way: Is there anyone successfully using this add-on with the ReadyNAS and UDP trackers? It's pretty much useless without it.

I was having the same problem until I downgraded to 2.23. Everything was fine until I upgraded from that version to 2.32 - any torrent with UDP trackers would not download at all.

I'm having the same problem. Some downloads seem to work ok, others don't. I don't know if it's because some are using HTTP trackers and some aren't, but I upgraded so I could use UDP trackers and performance now is very patchy. Is downgrading the only way? Does 2.23 still support UDP trackers?

try 2.34

I have the same issue on both 2.33 and 2.34b04 running 4.1.8 on my Duo.

I've spent the evening playing with this. I was running 2.32, now upgraded to 2.34b04 on a readynas duo running 4.1.7. I know it's not the latest firmware, but I'm loathed to upgrade it when I've got it running how I want. Well, nearly :-)

I made the error of uninstalling 2.32 before reinstalling 2.34, which meant I lost my settings file and so had to go about setting this up again. You'd think I'd remember, but again I've had to keep limiting the number of peers that can connect within transmission in order to keep the readynas on the network (if it's above a certain number - about 8 it appears - then the other computers on the network can't access it - either through frontview, or shares, or as networked drives - all I get is "Sorry, can't connect" errors. The only way I can get it back is to turn it off, unplug the router from the outside world, turn the duo back on, then access the transmission parameters, then plug the router back into the outside world and then hopefully find it all stays stable).

Anyway I did manage to download a whopping 2MB on one file (I'm just going one at a time), but the rest of the time I'm just getting "0 of 0 peers" connected and nothing happening. At least it's not the tracker not connected error I guess.

It's a shame because everything was running brilliantly with Transmission until I came across the need for UDP trackers.... I upgraded to 2.32 and got patchy success - time will tell what I have at the moment! If it doesn't work then I'll try downgrading to 2.23 if i can find the link.

In addition using the same torrent file in Transmission (1.9.3) on my Ubuntu laptop has connected to 14 of over 60 peers and immediately started downloading.

The Ubuntu laptop and Duo are connected on the same network and access the internet through the same router. The only difference is that the laptop connects wirelessly, and the duo connects through homeplugs. I do get a faster connection through the homeplugs than the wireless link.

Ok... the readynas did find up to about 5 peers (I have restricted the number, see above), but within about 15 minutes it's consistently disappearing from the network. I've disabled the addon. I will try 2.23 and see if that solves it when i get the chance.

Playing with transmission on my laptop has led to new questions though. Previously my readynas with transmission was "stable" on the network when I restricted the number of peers it could connect to. I thought this was because if it connected to too many then the router was removing it from the network (other computers on the network could no longer access it, either through web browser, as network drives, or using raidator). However having seen how many my ubuntu laptop can connect to - using transmission - then this already shakey premise looks even less likely (as the router isn't treating the laptop in the same way). So..... All ideas welcome ;-) At first glance I can't see anything different between how the two transmissions are set up, although the "encrypted peers" question is phrased slightly different and so the selections are different (on readynas duo - ignore unencrypted peers; on laptop - prefer encrypted peers)

Well. Downgraded to the transmission 2.31 add-on, as it was (from my understanding?) the last none beta release to support UDP.
It occassionally connects (very low speeds) but the NAS is getting disconnected from the network after about 5-10 minutes, consistently. The only way to stop it is to disable the add-on.

With 2.32 I had patchy performance but it was stable so long as I only had one torrent underway at any one time. This includes paused torrents. However I'm having trouble replicating that at this time.

At the same time running Transmission on my 8 year old Ubuntu laptop is - using the same torrent files - connecting straight away and achieving speeds I've never had going through readynas route. And not getting removed from the network.

I'm not necessarily worried about the speed, more the stability. I don't want the readynas disappearing from the network. At the moment I might investigate some automatic start up and shut down scripts for the ubuntu laptop and use that as the download manager instead of the readynas. But it's not really the way I want to go...... All thoughts and suggestions are welcome, I think I've long exhausted my understanding and am quickly reaching the end of my patience too!

Please however do not take this as a dig at the Transmission add-on, or Super-poisson, because it isn't. I know this is a port of the transmission software that super-poisson is working on and supporting in their own time. However Netgear sell their ReadyNas as able to operate as a download manager/bittorrent client, and supply it with an "official" add-on to do so. However it was unreliable in itself and, from looking around, doesn't really appear to be actively supported by Netgear themselves. So in my eyes if it wasn't for Super-poisson then Netgear wouldn't have the "right" to call this a feature of their system at all.... and I can't help but feel a little bit cheated by that fact. That in order to try and get a feature of their product working, I have to spend evenings badgering those that are working on this in their freetime in order to try and get some semblance of the performance that they market.

Rant over ;-)

I used to use Transmission happily on my NV+ until the new firmware betas to cope with OSX Lion. Now I can't get any version of Transmission to work—it simply won't connect to anything, although it reports that the port is open happily enough (daemon.log simply says that it can't connect to any of the trackers).

I tried running the latest beta but the web interface is b0rked in that version for me—anyone else seeing that? (Most of the buttons across the top of the screen are rendered as an un-styled HTML list, and can't be clicked).

I moved back down to 2.32 but still no joy connecting to anything. Transmission on my Mac (same network and connectivity) works just fine.