I'm setting up my Raspberry Pi to work as a headless torrent box, and I'm having some trouble putting it into service.
I've read a lot about a certain bug on the kernel that, since the Pi's ethernet and USB interfaces share the same bus, makes the Pi when having heavy use, just like a torrent client would cause.
I have also read about a lot of people who finally managed to solve it, but I could find a single post where I'd learn everything about how to make it work, like what image did they use, what did they needed to tweak it, what client did they use, did they have to set any special configuration option on it, like download/upload speed limits, or something... just scattered info about kernel patches, tuned up Wheezy imgages, but never a full explanation.
What I've tried so far, is to use a tweaked Debian Wheezy image (http://www.linuxsystems.it/2012/06/debi ... mal-image/) with a custom kernel which should solve the problem, and the Transmission-daemon client with the web interface. This image made the server run for a few longer (a couple hours instead of a few minutes) but it ended up causing a kernel panic like the "official" Squeeze image.
Please, could anyone tell us his experiences with torrents and Raspberry Pi? If we manage to find a definitive solution to this issue, I'll compile a guide to correctly install and configure a Raspberry Pi, and publish it here and a wiki page about this issue.
Thanks in advance.