From owner-freebsd-questions Sun Jun 23 19:31:11 2002 Delivered-To: freebsd-questions@freebsd.org Received: from infinity.aesredfish.net (ns1.aesredfish.net [65.168.0.12]) by hub.freebsd.org (Postfix) with ESMTP id 229A337B408 for ; Sun, 23 Jun 2002 19:30:49 -0700 (PDT) Received: from potentialtech.com (mhope-dhcp-65-168-1-181.dashfast.com [65.168.1.181]) by infinity.aesredfish.net (8.11.6/8.11.0) with ESMTP id g5O2UHr21892; Sun, 23 Jun 2002 22:30:18 -0400 Message-ID: <3D1685B1.4010405@potentialtech.com> Date: Sun, 23 Jun 2002 22:36:33 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc1) Gecko/20020502 X-Accept-Language: en-us, en MIME-Version: 1.0 To: BSD Freak Cc: FreeBSD Questions Subject: Re: Dummynet not working References: <1794eaa1798343.17983431794eaa@mbox.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG BSD Freak wrote: > Hi all, > > I'm relatively inexperienced when it comes to dummynet but I have read > the man page and lots more about it. Basically the situation is this: > We have a FreeBSD 4.5R router (with dummynet compiled in the kernel) > running a 64Kbps ISDN line to another site. The line is usually > saturated making access very slow and unreliable for some hosts on the > network. We have one host (192.168.0.50) on the network that is > particularly important and which requires priority access. So I added > the following rules, but this does not seem to help: > > ipfw pipe 1 config bw 64Kbit/s > ipfw queue 1 config pipe 1 weight 90 > ipfw queue 2 config pipe 1 weight 1 > ipfw add 400 queue 1 tcp from 192.168.0.50 to any > ipfw add 500 queue 2 ip from any to any > > > What am I doing wrong? I delayed posting this because I'm not sure this answer is correct. I think you need to have both in and out traffic handled or your priority won't work, because outgoing traffic will be at higher prioriy, but incomming will be relegated to the lower priority, thus your overall priority won't be improved any. Maybe something like: ipfw pipe 1 config bw 64Kbit/s ipfw queue 1 config pipe 1 weight 90 ipfw queue 2 config pipe 1 weight 1 ipfw add 400 queue 1 tcp from 192.168.0.50 to any ipfw add 450 queue 1 tcp from any to 192.168.0.50 ipfw add 500 queue 2 ip from any to any See if that helps. And again, I'm not sure I have the right answer for you, so take it with a grain of salt. Also, make sure the traffic you're trying to prioritize is travelling on tcp, if not, it will be running at the lower priority. -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message