Weird - 3 computers, same network, one stops downloading

Discussion of Transmission that doesn't fit in the other categories
Post Reply
greg.harvey
Posts: 3
Joined: Thu Apr 01, 2010 8:16 am
Location: Uzès, France

Weird - 3 computers, same network, one stops downloading

Post by greg.harvey »

Hi all,

Got Transmission installed on 3 separate machines, one runs Fedora 13, one Fedora 10 and one Fedora 12. All three have been fine forever. But yesterday the Fedora 12 machine (Transmission 1.93) stopped being able to download or seed files. It's not my ISP, because the other two computers are unaffected, using the same gateway on the same LAN. The Fedora 12 machine just has all torrents 'Idle', it sees trackers and other peers, but it can't connect to them. Because it's Fedora 12 I can check 'yum history transmission' and it shows no updates have happened. Tried changing port too, just in case, again no joy.

Anyone have any idea what would stop a single machine on a network with Transmission stop being able to seed or leach when all other machines on the same LAN with the same OS and Transmission settings have no problems? :shock:

Thanks!
greg.harvey
Posts: 3
Joined: Thu Apr 01, 2010 8:16 am
Location: Uzès, France

Re: Weird - 3 computers, same network, one stops downloading

Post by greg.harvey »

Update: Downloaded Deluge, just to try and see if it was client-related, and Deluge fails too. Seems it's some computer/network setting? But I can't think I would've changed anything. I also shut down anything else that might get in the way, but still no joy.

Further update: I deleted ~/.config/transmission just in case, but that didn't help either. :(
rb07
Posts: 1400
Joined: Sun Aug 24, 2008 3:14 am

Re: Weird - 3 computers, same network, one stops downloading

Post by rb07 »

Are you using MoBlock? That one gave me problems over the weekend, similar to what you describe, plus I couldn't ftp to my server (it connected, logged in, no directory listing).

I didn't investigate further, just stopped it. My guess is that it added private IP address space to the firewall, stopping all traffic inside local LANs, I've seen it do that before (with 10.x.x.x, now it was with 192.168.x.x).
Post Reply