From owner-freebsd-bugs@FreeBSD.ORG  Sun Mar  7 02:34:59 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A634B16A4CE
	for <freebsd-bugs@freebsd.org>; Sun,  7 Mar 2004 02:34:59 -0800 (PST)
Received: from amsfep13-int.chello.nl (amsfep13-int.chello.nl [213.46.243.24])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D104443D2D
	for <freebsd-bugs@freebsd.org>; Sun,  7 Mar 2004 02:34:58 -0800 (PST)
	(envelope-from dodell@sitetronics.com)
Received: from sitetronics.com ([213.46.139.145]) by amsfep13-int.chello.nl
          (InterMail vM.6.00.05.02 201-2115-109-103-20031105) with ESMTP
          id <20040307103457.MZDF8266.amsfep13-int.chello.nl@sitetronics.com>;
          Sun, 7 Mar 2004 11:34:57 +0100
Message-ID: <404AFA1F.20307@sitetronics.com>
Date: Sun, 07 Mar 2004 11:31:59 +0100
From: "Devon H. O'Dell" <dodell@sitetronics.com>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ender <ender@tog.net>, freebsd-bugs@freebsd.org
References: <404AEF20.7090506@tog.net> <404AF34B.7000506@sitetronics.com>
	<404AFA96.5070507@tog.net>
In-Reply-To: <404AFA96.5070507@tog.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: bad syntax in ipfw casues kernel panic.
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Mar 2004 10:34:59 -0000

Ender wrote:

> try these rules
>
> ipfw pipe 1 config bw 800Kbyte/s queue 1024Kbytes ;
> ipfw queue 1 config pipe 1 weight 100 queue 1024Kbytes ;
> ipfw queue 2 config pipe 1 weight 90 queue 1024Kbytes ;
> ipfw queue 3 config pipe 1 weight 2 queue 1024Kbytes ;
> ipfw queue 4 config pipe 1 weight 1 queue 1024Kbytes ;
> ipfw add 1 queue 1 udp from 216.89.228.18 27015 to any out ;
> ipfw add 2 queue 2 tcp from 216.89.228.18 6112 to 216.89.228.60 out ;
> ipfw add 3 queue 3 ip from 216.89.228.18 6112 to any out ;
> ipfw add 4 queue 4 ip from 216.89.228.18 to any out ;
>
> then remove : ipfw del 1
> then remove ipfw queue del 1
> then add ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes

When I add these rules, and hit the final one, I receive:
root@freebsd0 :~# ipfw queue 1 config pipe 1 weight 140 queue 1024Kbytes
ipfw: weight must be <= 100

Before you question my system:
FreeBSD freebsd0.sitetronics.com 5.2.1-RELEASE-p1 FreeBSD 
5.2.1-RELEASE-p1 #2: Wed Mar  3 09:25:48 PST 2004     
root@freebsd0.sitetronics.com:/usr/obj/usr/src/sys/SITETRONICS  i386

>
> i also have ALOT of traffic when i do this, i repeated it. If there is 
> any other configs i have that could be relevent let me know.

What's ``A LOT'' of traffic? The system I'm on is pushing approximately 
10Mbit at this time.

> kern.ipc.somaxconn=16384
> kern.ipc.nmbclusters=131072
> net.inet.tcp.tcbhashsize=4096
>
>
> #firewall
> options         HZ=1000
> options         IPFIREWALL
> options         IPFIREWALL_DEFAULT_TO_ACCEPT
> options         DUMMYNET

These all look decent to me.

--Devon