Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1911 closed Bug (worksforme)

Transmission randomly does not respond on the designated listening port

Reported by: krx Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.51
Severity: Minor Keywords: port not listen listeing designated default respond
Cc:

Description

Transmission randomly does not respond on the designated listening port. Port is default - 51413. The failure:success ratio is from ~1:1 to ~6:1 sometimes. I check say with http://www.utorrent.com/testport.php?port=51413 or http://www.canyouseeme.org. When I started using Transmission, I have used these services to double-check the configuration and it was OK.

I think this bug started in 1.51 version. I have noticed it because Transmission was not able to participate in the private trackers systems, where connection to the tracker is essential for UL/DL accounting.

I have started Transmission in the command line mode, it did not output any specific messages, when probing with the services mentioned above.

To my knowledge, nothing has changed, except the transmission upgrade from 1.50->1.51 ~10 days ago. Firewall configuration is the same as it was about half a year before.

Change History (6)

comment:1 Changed 12 years ago by livings124

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

Well, that code has not changed in a long time. Regardless, the port forwarding code is miniupnp (http://miniupnp.tuxfamily.org/), so I would report any problems there.

comment:2 Changed 12 years ago by krx

  • Resolution invalid deleted
  • Status changed from closed to reopened

Port forwarding is not used. Transmission daemon is running on the router itself, router has real fixed IP. Firewall ports are open.

comment:3 follow-up: Changed 12 years ago by livings124

Are you saying it isn't connecting to the tracker? Are you sure this is related to the port? Are you sure it's not the tracker rejecting you/being down? (What do you mean by not able to "participate"?) I don't think the changes in 1.51 should have an impact on anything like this.

comment:4 in reply to: ↑ 3 Changed 12 years ago by krx

Replying to livings124:

Are you saying it isn't connecting to the tracker?

I do not know specifics of the Bittorent protocol, therefore I can not speculate very deeply. I only see, that tracker most of the time does not see me as the client.

Are you sure this is related to the port?

It is not related to port. I only see, that Transmission daemon does not respond to the outside probes.

Are you sure it's not the tracker rejecting you/being down? (What do you mean by not able to "participate"?)

That is possible. Yet, I do not have any indications, that transmission is hanged or smth. like that, because it responds locally, say to webinterface or "transmission-remote -l". But it does not respond on the external interface most of the time.

I don't think the changes in 1.51 should have an impact on anything like this.

I am not sure, is this problem is isolated to 1.51. I only speculated about that.

comment:5 Changed 12 years ago by livings124

  • Resolution set to worksforme
  • Status changed from reopened to closed

I am really confused by this ticket, but no one else is reporting anything like this. I suspect it is a problem with either the tracker or user-confusion.

comment:6 Changed 12 years ago by krx

  • Severity changed from Normal to Minor

1.51 version had this bug for sure. I have upgraded to the 1.52 a few days ago, this bug does not repeat itself. I think it is not worth to find bug in 1.51, because Transmission development is fast and this imposes the idea to upgrade often.

Note: See TracTickets for help on using tickets.