From owner-freebsd-net@FreeBSD.ORG Sun Jun 29 07:43:20 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 255D7106566B for ; Sun, 29 Jun 2008 07:43:20 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id D2EFF8FC0C for ; Sun, 29 Jun 2008 07:43:19 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so462979ywe.13 for ; Sun, 29 Jun 2008 00:43:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=KXOPcJMMfP912j3AjkGlaftnNG0KoVpYoyZYi+cyhyU=; b=dZHa99RKggt+dzbaE5RD/O5RAMft58rcs3KodLQq/NPqRA5vD+XAW/LA0hu3FT1EpB sd9V5N9hqAjz1z3eCS77ZclDbiu2JS8CB89vTjJBVHYpdpEyZec+7CdeIGA/w5+DLN1B FYaUqxtriRkN11Pdz7PWvi0XsTsE9C+PJadzI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wKoDF15wX778tZUdiF9GNojWMpPwKchoDKy44ntrPj60592rzk4Tei1GE0wEet/+j3 3ZXJlGO/qVIuwUe2KD15VKu1Smn3AZ/AMpKXDlfm5GogDzwyQLQciSVKgn2lRARZ2XtA UPiPFhCALgKWkrzqfoOszpAWYNAxAGuYmweAA= Received: by 10.150.137.9 with SMTP id k9mr5807614ybd.216.1214725398742; Sun, 29 Jun 2008 00:43:18 -0700 (PDT) Received: by 10.151.154.17 with HTTP; Sun, 29 Jun 2008 00:43:18 -0700 (PDT) Message-ID: Date: Sun, 29 Jun 2008 00:43:18 -0700 From: "Freddie Cash" To: freebsd-net@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: Understanding where dummynet fits into an ipfw ruleset X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jun 2008 07:43:20 -0000 On Sat, Jun 28, 2008 at 11:22 PM, Ian Smith wrote: > It's not clear to me what's not working from your example rules above? I never said anything wasn't working. I was just looking for information to better understand how things work together, and to get a general feeling of where the queue rules would have to go. > Given using one_pass=1, that should go. And using one_pass=0, you > should only need to also add as say rule 150: > > 150 allow ip from 1.1.1.1 to 2.2.2.2 in recv em0 I'm starting to better understand how one_pass affects things. And I think I get, now, where to put the queue rules. I won't be doing any of the actual testing or implementation until July. I was just looking for more info on how to set things up. > > > Yes I suspect Freddie might want to use pipe rather than queue here too, > > > if just for bandwidth limitation rather than weighted queueing by type > > > of traffic? And is it only wanted for managing the inbound traffic? > > > > No, I want to use queue. I want to create rules to "reserve" > > bandwidth for connections to important servers, as we're moving to > > more web-based applications, and I want to make sure students surfing > > the web don't impact office staff. There will be a single pipe, with > > two queues, one weighted at twice the value of the other. That way, > > if there is no staff traffic, the students get the whole pipe. If > > there is no student traffic, staff get the whole pipe. And if there's > > a mix, then staff traffic is prioritised ahead of student traffic. > > Ok; on rereading your original, I should have realised that. So with a > similar set of rules for the other of staff/students that your above > example deals with, and the right pipe and queue configs, what remains > to do? Sorry to be thick, but I don't see why that wouldn't work .. I never said it wouldn't (or didn't) work. :) -- Freddie Cash fjwcash@gmail.com