From owner-freebsd-questions@FreeBSD.ORG Thu Nov 27 17:49:12 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B4AB16A4CE for ; Thu, 27 Nov 2003 17:49:12 -0800 (PST) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92E0143FCB for ; Thu, 27 Nov 2003 17:49:11 -0800 (PST) (envelope-from timothy@voidnet.com) Received: from repose (c-24-0-112-81.client.comcast.net[24.0.112.81]) by comcast.net (rwcrmhc13) with SMTP id <2003112801490901500pp5jce>; Fri, 28 Nov 2003 01:49:10 +0000 From: Eric Timme To: freebsd-questions@freebsd.org Date: Thu, 27 Nov 2003 19:49:07 -0600 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311271949.07701.timothy@voidnet.com> Subject: Kazaa/p2p on a LAN and ping problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2003 01:49:12 -0000 Network topology: LAN <==> FreeBSD Gateway <==> Internet Gateway specifications: FreeBSD overlord 4.8-STABLE FreeBSD 4.8-STABLE #0: Mon Sep 22 07:05:09 CDT 2003 k6-233, 128MB ram ipf packet filtering in place Internet (cable): 256kb up 2.0mbish down ====== It seems an impossible task to limit Kazaa and other p2p (Kazaa especially) from accessing the Internet from a LAN, especially when you're sharing the LAN with other college age people. So, I've instead told them to limit their upstream to 5kB, which leaves a good amount of of the upstream pipe for web browsing. However, whenever any p2p in the house is active pings on any external network degrade horribly, even if it's only a single host, and 20kb of my upstream bandwith remains. Wolfenstein servers that I pinged 30 on with no p2p activity on the LAN, for instance, begin to ping at 400-500 ; the situation is equally bad with MUDs and other ping reliant games such as Quake. Is this normal? Is there anything I can do to fix the problem so that ping dependant games can be played while p2p apps are active on the LAN? Kicking the network cable out works late at night, and at times during the day, but it isn't a permanent solution. Limiting p2p from the LAN completely is not possible from my position. A user on IRC mentioned he had no such problem with IPFW - if my problem isn't specific does that mean that my use of ipf is responsible for this behavior? Thanks, Eric