Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1257 closed Enhancement (invalid)

Test port only upon user request, and distinguish closed and unknown states

Reported by: jidanni Owned by:
Priority: Lowest Milestone: None Set
Component: Transmission Version: 1.33
Severity: Trivial Keywords:
Cc:

Description

I found a wiki page but not edit button, so please on the top of http://trac.transmissionbt.com/wiki/Why is my port closed (P.S., you guys love spaces in hyperlink names, you'll be sorry one day...) please mention

Q: In Preferences->Peers it says "Port is close" (d 3/4 chopped off: bug!)

However, I still get great upload and download speeds. Do I still need to read this page? If not why not?

A: No you needn't bother to read this page, and no I don't know why not...

Change History (4)

comment:1 Changed 13 years ago by charles

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

This is incorrect. Peers that are not connectible are bad for the swarm.

comment:2 Changed 13 years ago by jidanni

  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Summary changed from Document that port closed is OK sometimes to Test port only upon user request, and distinguish closed and unknown states

Also there are privacy concerns with the design of Preferences>Peers. There should be a "test the port now" button so the user can explicitly test, rather than the current "web bugs images" design where just viewing the page causes transmission to "light up the network calling home to mother etc." or whatever it does.

And indeed, as I am getting super download speeds (using 90% of my connection's (piddling 256/64KB ADSL) capacity) then my port must be open and the message that it is closed is wrong in the first place. I bet/guess there are actually three states: open, closed, and unknown, and the latter gets lumped into "closed". Unknown would be where tests don't complete because the user is running moblock, iptables, etc.

And I recall when I really did clog up my port with wrong iptables, connections would all be slower than 1 KB/s.

OK, reopening with two new concepts in title, not that they might be worthy.

comment:3 Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from reopened to closed
And indeed, as I am getting super download speeds (using 90% of my connection's (piddling 256/64KB ADSL) capacity) then my port must be open and the message that it is closed is wrong in the first place.

The two have nothing to do with each other. You don't know what you're talking about.

comment:4 Changed 13 years ago by jidanni

Anyways, I conclude that the transmisson "testing...port is closed" is inacurate, as http://canyouseeme.org/ says Success: I can see your service on 122.127.43.244 on port (51413) Your ISP is not blocking port 51413

Note: See TracTickets for help on using tickets.