From owner-freebsd-pf@FreeBSD.ORG Sun Nov 14 03:53:52 2004 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F32B616A4D0 for ; Sun, 14 Nov 2004 03:53:51 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 517D543D49 for ; Sun, 14 Nov 2004 03:53:51 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CTBSX-0008Ah-00; Sun, 14 Nov 2004 04:53:49 +0100 Received: from [217.227.156.235] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CTBSX-0004Oz-00; Sun, 14 Nov 2004 04:53:49 +0100 From: Max Laier To: freebsd-pf@freebsd.org Date: Sun, 14 Nov 2004 04:53:57 +0100 User-Agent: KMail/1.7.1 References: <000301c4c9c3$8e9c9a50$320a0a0a@uranus> In-Reply-To: <000301c4c9c3$8e9c9a50$320a0a0a@uranus> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4402261.pMUyUfQ44X"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411140454.04402.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: Shane James Subject: Re: FreeBSD ALTQ + PF Problem X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical discussion and general questions about packet filter (pf) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 03:53:52 -0000 --nextPart4402261.pMUyUfQ44X Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 13 November 2004 21:58, Shane James wrote: > Hey guys, > > I'm having a problem with pf + altq on FreeBSD 5.2.1 (FreeBSD > uplink-rtr-jhb.virtek.co.za 5.2.1-RELEASE-p11 FreeBSD 5.2.1-RELEASE-p11 #= 1: > Sat Nov 13 15:59:38 SAST 2004 > root@uplink-rtr-jhb.virtek.co.za:/usr/src/sys.altq/i386/compile/UPLINK > i386) > > The Traffic I assign to queue's does not get limited according to the > specific limit, it only get's limited by the global bandwidth limited > assign to the specific NIC. > e.g. I assign traffic to a queue(argon_d) which is limited to 128Kb... but > it performs at 256Kb which is what the NIC is set to. therefore not being > assigned to it's designated queue. is it at all possible that this is a > problem perhaps with my Network cards... if not... any suggestions? > > pf.conf > > altq on $uplink_if bandwidth 256Kb hfsc queue { dflt_u, argon_u } > queue argon_u hfsc(realtime 64Kb upperlimit 64Kb) > queue dflt_u hfsc(default upperlimit 128Kb) > > altq on $hosting_if bandwidth 256Kb hfsc queue { dflt_d, argon_d } > queue argon_d hfsc(realtime 64Kb upperlimit 64Kb) > queue dflt_d hfsc(default upperlimit 128Kb) > > #assign argon traffic > pass out on $uplink_if from 196.23.168.137 to any keep state queue argon_u > pass out on $hosting_if from any to 196.23.168.137 keep state queue argon= _d I assume that is not your *complete* ruleset?!? Can everybody please post=20 complete rulesets when asking for help? It is okay to emphasize the parts=20 that you think are important as it will help to understand the problem, but= =20 giving advice or debugging it impossible without the complete ruleset. Other than that, what does "$pfctl -vvsq" tell you? Does it show that traff= ic=20 is being assigned to the small queue at all? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart4402261.pMUyUfQ44X Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBltbcXyyEoT62BG0RAiX1AJ0d6yJH3PSdwhGrv2ehJpNiPi0/2ACeOK1C HPcfgHkKEp1ekfwVRPpF3Kc= =K1CS -----END PGP SIGNATURE----- --nextPart4402261.pMUyUfQ44X--