Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#4639 closed Bug (invalid)

Transmission wont stop communication

Reported by: facsi Owned by:
Priority: High Milestone: None Set
Component: Transmission Version: 2.42
Severity: Normal Keywords: wont stop communication
Cc:

Description

Hi, Im using a DD-WRT version of transmission and it has this annoying bug. It is impossible to stop seeding a torrent. It wont stop even after deleting the torrent from the list. My list is empty and my router keeps doing some strange communication (I think its seeding). It only stops after I kill the optware or reboot the router. Im on 2.42.

Change History (10)

comment:1 Changed 9 years ago by livings124

Are you sure those aren't just peers still trying to connect to Transmission. We can't do anything about what other clients do.

comment:2 Changed 9 years ago by jordan

It's possible that there may be some upload data queued up that still gets processed, but even if that happens it should work through the system in a few seconds.

If you're seeing ongoing communication long after the torrent is stopped or removed, please see https://forum.transmissionbt.com/viewtopic.php?p=42451#p42451 and https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/577657/comments/3 , I believe those explain what extra network activity is happening.

comment:3 Changed 9 years ago by facsi

I can make a video about it if necessary. My thoughts are: When I use uTorrent or anyother torrent software, I click stop (or delete torrent) and all communications are ceased. Cant Transmission do the same? When I go to Security->Incoming log on ddwrt I see a lot of peers on the port I choosed for transmission. But if I keep clicking refresh no peer are the same. I think that they are connecting and disconnecting because there was to file to seed (paused or torrent deleted).

comment:4 Changed 9 years ago by livings124

Transmission has no control over what's incoming. Even if the app shuts down properly, peers might still attempt to send and receive data from us. Transmission does announced that it's stopping transfers, but it takes a while for peers to know that the client isn't still seeding.

comment:5 Changed 9 years ago by facsi

I see. Someday I let it overnight and it didnt stop. The thing is: When I restart it, the IP is the same, port is the same, but the incoming connections are stopped. Then somehow transmission can control incoming connections ;)

comment:6 Changed 9 years ago by livings124

Are there any outgoing connections? That's what we have control over. I'm no network expert, but I'm guessing when you restart something's changed.

comment:7 Changed 9 years ago by facsi

I didnt see any connections on ddwrt outgoing log before and after closing transmission. Im going to restart transmission without deleting the torrent to see if it returns doing communications.

Edit 2: I did further testing. I was wrong. I rebooted everything here. Router and modem = new ips. PCs shut off. with mobile I checked dd-wrt: No connections. No activity. Then I started transmission without torrents: Connections started and so activity. Seems correct as you wrote before. That said, there isnt a way to stop it having transmission opened?

Last edited 9 years ago by facsi (previous) (diff)

comment:8 Changed 9 years ago by facsi

  • Resolution set to invalid
  • Status changed from new to closed

comment:9 follow-up: Changed 9 years ago by x190

"That said, there isnt a way to stop it having transmission opened?"

If you use DHT, traffic will be continuous as long as the daemon is running.

comment:10 in reply to: ↑ 9 Changed 9 years ago by facsi

Replying to x190:

"That said, there isnt a way to stop it having transmission opened?"

If you use DHT, traffic will be continuous as long as the daemon is running.

Thanks!

Note: See TracTickets for help on using tickets.