From owner-freebsd-current@FreeBSD.ORG Tue Oct 14 06:20:30 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 845D416A4B3 for ; Tue, 14 Oct 2003 06:20:30 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD4E43F85 for ; Tue, 14 Oct 2003 06:20:29 -0700 (PDT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1A9P61-0003Ar-00; Tue, 14 Oct 2003 15:20:17 +0200 Received: from [217.83.7.147] (helo=max2400) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1A9P61-0003Ze-00; Tue, 14 Oct 2003 15:20:17 +0200 Date: Tue, 14 Oct 2003 15:20:41 +0200 From: Max Laier X-Mailer: The Bat! (v2.00.6) X-Priority: 3 (Normal) Message-ID: <406622109.20031014152041@love2party.net> To: Michael Nottebrock In-Reply-To: <200310141403.55012.michaelnottebrock@gmx.net> References: <200310141045.09755.michaelnottebrock@gmx.net> <200310141403.55012.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-altq@rofug.ro cc: current@freebsd.org Subject: Re: [ALTQ/FreeBSD] Re: if_tun not altq enabled in pfaltq patch? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Max Laier List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Oct 2003 13:20:30 -0000 Hello Michael, Tuesday, October 14, 2003, 2:03:51 PM, you wrote: >> I see it's patched and contains altq-code, but trying to apply the classic >> ack-prioritizing ruleset gives me "pfctl: tun0: driver does not support >> altq". Is this expected? MN> Okay, it seems pf didn't like the fact that my if_tun was a module. In-kernel MN> seems to work. Yes, that is a general problem: We'd have to extensively patch all if_* module Makefiles to propagate the new option. There is: > +------------------------------------------------------------------------+ > | Issue | Status | Responsible | Description | > |---------------------+-----------+-----------------+--------------------| > | | | | Kernel modules are | > | | | | currently built | > | | | | independently from | > | | | | a kernel | > | | | | configuration, and | > | | | | independently from | > | | | | one another, | > | | | | resulting in | > | | | | substantially | > | | | | redundant | > | | | | compilation of | > | | | | objects, as well | > | | | | as the inability | > | | | | to easily manage | > | | | | compile-time | > | | | | options for kernel | > | | | | objects (such as | > | | | | MAC, PAE, etc) | > | Revised kld build | -- | -- | that may require | > | infrastructure | | | conditional | > | | | | compilation in the | > | | | | kernel modules. In | > | | | | order to improve | > | | | | build performance | > | | | | and better support | > | | | | options of this | > | | | | sort, the KLD | > | | | | build | > | | | | infrastructure | > | | | | needs to be | > | | | | revamped. Peter | > | | | | Wemm has done some | > | | | | initial | > | | | | prototyping, and | > | | | | should be | > | | | | contacted before | > | | | | starting on this | > | | | | work. | > |---------------------+-----------+-----------------+--------------------| this topic from the 5.2-Release TODO applies here! If you are planning to investigate in that area, I could offer some starting points. I am unsure how to do this "right" so I didn't start anything myself, but I have some ideas ... If anybody is going to put his head into it, feel free to contact me for support. -- Best regards, Max mailto:max@love2party.net