Firewall Wizards mailing list archives
Re: Port numbers for Peer to Peer file sharing apps.
From: Eric Vyncke <evyncke () cisco com>
Date: Fri, 22 Nov 2002 10:55:49 +0100
At 10:50 22/11/2002 +0100, Mikael Olsson wrote:
Eric Vyncke wrote:If you are concerned only by the waste of bandwidth, you may want to: - block all incoming TCP connections but the really needed onesUm. That doesn't work for kazaa (fasttrack), gnutella, etc. These apps will detect if they're firewalled, and if two peers want to talk to eachother where one side is firewalled, the connection will always be initiated by the firewalled one.
Right, but my point was that those applications require at least one peer without firewall (= accepting incoming connection). So, blocking incoming connections will cut the bandwidth by at least 50% (as a lot of P2P users are behind NAT or firewalls)
(And for public networks, every port is "needed" if you ask the users.)
Agreed, you then get what you want ;-) -eric _______________________________________________ firewall-wizards mailing list firewall-wizards () honor icsalabs com http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
Current thread:
- Port numbers for Peer to Peer file sharing apps. Mark Whobrey (Nov 20)
- Re: Port numbers for Peer to Peer file sharing apps. Tony Howlett (Nov 20)
- Re: Port numbers for Peer to Peer file sharing apps. Mikael Olsson (Nov 21)
- Re: Port numbers for Peer to Peer file sharing apps. Eric Vyncke (Nov 22)
- Re: Port numbers for Peer to Peer file sharing apps. Mikael Olsson (Nov 22)
- Re: Port numbers for Peer to Peer file sharing apps. Eric Vyncke (Nov 22)
- Re: Port numbers for Peer to Peer file sharing apps. Eric Vyncke (Nov 22)
- <Possible follow-ups>
- RE: Port numbers for Peer to Peer file sharing apps. James Paterson (Nov 22)