From owner-freebsd-isp@FreeBSD.ORG Fri Feb 27 10:26:13 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56ED916A525 for ; Fri, 27 Feb 2004 10:26:13 -0800 (PST) Received: from telcommail.net (mail.telcom.net [200.80.13.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC2F243D39 for ; Fri, 27 Feb 2004 10:26:12 -0800 (PST) (envelope-from akachler@telcom.net) Received: from telcom.net (host203.216.22.121.telcom.net [216.22.121.203] (may be forged)) by telcommail.net (8.12.10/8.12.10) with ESMTP id i1RILoM9045826 for ; Fri, 27 Feb 2004 13:21:51 -0500 (EST) Message-ID: <403F8B75.4010903@telcom.net> Date: Fri, 27 Feb 2004 13:24:53 -0500 From: Arie Kachler User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isp@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: re: p2p traffic X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2004 18:26:13 -0000 Thomas, I don't know of a FreeBSD-based solution to this problem. But Packeteer makes devices that do what you're looking for. See http://www.packeteer.com/prod-sol/products/packetseeker.cfm. Hope it helps. Arie Kachler >Hello > >I'm thinking about the p2p network problem. P2p creates a lot of >traffic. I don't care if my backbone is full but not only with p2p >traffic. Atm I do some queueing with dummynet for the well known p2p >ports. But this looks not sufficient. Is there another, perhaps better >solution to decrease the p2p traffic? Blocking is no alternative. >Another problem is that new p2p clients uses port 80. So it's very >difficult to reconize the p2p traffic. > >regards >Thomas Vogt >