From owner-freebsd-pf@freebsd.org Mon Oct 16 13:03:17 2017 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDBC2E3A5C3 for ; Mon, 16 Oct 2017 13:03:17 +0000 (UTC) (envelope-from R.Dahmen@m3connect.de) Received: from mailout-f3.arcor-ip.de (mailout-f3.arcor-ip.de [145.253.3.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 777B7802E7 for ; Mon, 16 Oct 2017 13:03:17 +0000 (UTC) (envelope-from R.Dahmen@m3connect.de) Received: from MX01.scientific.de (unknown [88.79.237.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout-f3.arcor-ip.de (Arcor-IP) with ESMTPS id 248C9B43D0B for ; Mon, 16 Oct 2017 14:54:31 +0200 (CEST) Received: from MX01.scientific.de ([::1]) by MX01.scientific.de ([::1]) with mapi id 14.03.0361.001; Mon, 16 Oct 2017 14:55:04 +0200 From: Rolf Dahmen To: "freebsd-pf@freebsd.org" Subject: Issue using altq_priq unter FreeBSD 11.1 - help needed Thread-Topic: Issue using altq_priq unter FreeBSD 11.1 - help needed Thread-Index: AdNGfTkcET+ejV+PRBaL9i1p4eqGCA== Date: Mon, 16 Oct 2017 12:55:03 +0000 Message-ID: <201C56274507CA41A05709BADF3703F3761C03@MX01.scientific.de> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [192.168.13.85] MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.23 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: Mon, 16 Oct 2017 13:03:17 -0000 Hi all, I=B4m Rolf Dahmen working as CTO for a german Wifi Service Provider. We do = have a certain issue that we are not able to configure QoS to prioritize qu= eues on FreeBSD using pf with altq. My SysOps engineers are stuck in gettin= g it done, so I`m looking forward to get a resolution or any consults onboa= rded. We have successfully recompiled the kernel to use pf with altq. We have configured 5 new queues "allowed, specialip, terminals, freeunlimit= ed, free" to pass the incoming traffic to prioritize the flow. The issue is= that always the defined default queue is used but never the user queues. I do think that our pf.conf is not complete: (pf.conf) altq on igb0 priq queue {allowed, specialip, terminals, freeunlimited, free= } queue free priority 5 priq(red) queue freeunlimited priority 4 priq(red) queue terminals priority 3 priq(red) queue specialip priority 2 priq(red) queue allowed priority 1 priq(default red) Gru=DF, Rolf Dahmen Chief Technology Officer (CTO) [cid:image001.jpg@01D168B7.D9C957D0] T: +49 (0)241 980 986 68 M: +49 (0)151 617 196 23 Fax: +49 (0)241 980 986 90 Web: www.m3connect.de E-Mail: r.dahmen@m3connect.de m3connect GmbH | Friedlandstr.18 | 52064 Aachen | DE/Germany | Amtsgericht = Aachen | HRB 8773 | USt.- ID: DE219 664 658 | Gesch=E4ftsf=FChrer/CEO: Emil= io Dragas, Markus Schindler