BitTorrent macro should use ports 6881:6999, not only 6881:6889

Bug #110873 reported by Daniel Hahler
8
Affects Status Importance Assigned to Milestone
shorewall-common (Ubuntu)
Won't Fix
Wishlist
Unassigned

Bug Description

Binary package hint: shorewall

The BitTorrent macro uses ports 6881-6889, but should really use ports 6881-6999 (which gets used by BitTorrent since version 3.2). Additionally, the rtorrent client uses 6890-6999, because the default ports are blocked often.

Revision history for this message
Craig73 (funrun73) wrote :

Posted request to mailing list at http://www.shorewall.net/ [to ask if they would consider this request]

Changed in shorewall:
status: New → Confirmed
Hew (hew)
Changed in shorewall:
importance: Undecided → Wishlist
Revision history for this message
Craig73 (funrun73) wrote :

Shorewall Guy wrote:
> Craig Kingston wrote:
>> My apollogies if this is not the correct forum, we have an old request
>> in our problem tracker to modify the default ports in macro.Bittorrent
>> to reflect the ports used in the recent versions of Bittorrent. Is
>> this something you would consider doing for a future release? What
>> would be the appropriate process to request this?
>>
>
> Craig,
>
> This type of request is better handled on the Shorewall Development
> mailing list.
>
> Be that as it may, the comments in the current macro file reflect our
> decision about an earlier request to enlarge the Bittorrent port range.
> Are we to understand from this request that the Bittorrent community has
> now decided to grab yet another 100 ports? If so, that definitely
> strengthens our resolve to not be a party to this continuing escalation.

I've updated the comment in both the 4.0 and 4.2 macros to specify
6881:6999 rather that 6881:6899.

Revision history for this message
Craig73 (funrun73) wrote :

FWIW - I did a quick search and there are those who advocate not even using the default port range due to ISPs blocking ports.

Future Ubuntu releases should pick up these changes to the comments (as they are packaged by debian and flow downstream) but the defaults will not change.

Revision history for this message
C de-Avillez (hggdh2) wrote :

Given upstream position [1], I am marking this as won't fix. I see no plausible reason to create a local patch.

Changed in shorewall-common:
status: Confirmed → Won't Fix
Revision history for this message
C de-Avillez (hggdh2) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.