Opened 10 years ago

Closed 10 years ago

#4322 closed Bug (fixed)

It is unobvious if test port feature tests UDP port status as well

Reported by: Username Owned by: jordan
Priority: Normal Milestone: 2.33
Component: Transmission Version: 2.31
Severity: Minor Keywords:
Cc:

Description

As far as I understand, T uses UDP port for uTP and DHT + TCP port for old-style classic/compatible bittorrent operation. So there are at least 2 different ports in use, one TCP and one UDP. However, "test port" button of GTK+ client only outputs one status, and even does not tells for which port this status goes. This makes firewalls/NATs troubleshooting tricky as you even don't really know which port(s) has been tested. It looks like if this thing should be a bit more explicit and verbose on what it doing and which results were obtained.

Change History (3)

comment:1 Changed 10 years ago by jordan

  • Component changed from Transmission to GTK+ Client
  • Owner set to jordan
  • Severity changed from Normal to Minor

comment:2 Changed 10 years ago by jordan

  • Status changed from new to assigned

comment:3 Changed 10 years ago by jordan

  • Component changed from GTK+ Client to Transmission
  • Milestone changed from None Set to 2.33
  • Resolution set to fixed
  • Status changed from assigned to closed

Fixed for GTK+ and Qt clients in r12550.

Note: See TracTickets for help on using tickets.