From owner-freebsd-pf@FreeBSD.ORG Thu Sep 16 03:43:04 2004 Return-Path: Delivered-To: freebsd-pf@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 674) id 7AA5C16A4CF; Thu, 16 Sep 2004 03:43:04 +0000 (GMT) Delivered-To: mlaier@vampire.homelinux.org Received: (qmail 40816 invoked by uid 1005); 3 Aug 2003 23:03:59 -0000 Delivered-To: max@vampire.homelinux.org Received: (qmail 40813 invoked from network); 3 Aug 2003 23:03:59 -0000 Received: from moutng.kundenserver.de (212.227.126.185) by pd953052f.dip.t-dialin.net with SMTP; 3 Aug 2003 23:03:59 -0000 Received: from [212.227.126.211] (helo=mxng15.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19jSmI-0008Lu-00 for max@vampire.homelinux.org; Mon, 04 Aug 2003 02:00:42 +0200 Received: from [206.53.239.180] (helo=turing.freelists.org) by mxng15.kundenserver.de with esmtp (Exim 3.35 #1) id 19jSmE-0001wU-00 for max@love2party.net; Mon, 04 Aug 2003 02:00:38 +0200 Received: from turing (localhost [127.0.0.1])ESMTP id 6A643395182; Sun, 3 Aug 2003 19:05:14 -0500 (EST) Received: with ECARTIS (v1.0.0; list pf4freebsd); Sun, 03 Aug 2003 19:05:10 -0500 (EST) Delivered-To: pf4freebsd@freelists.org Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.185])ESMTP id 0274E39503E for ; Sun, 3 Aug 2003 19:05:08 -0500 (EST) Received: from [212.227.126.160] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19jSm6-0008Js-00 for pf4freebsd@freelists.org; Mon, 04 Aug 2003 02:00:30 +0200 Received: from [217.83.5.47] (helo=max900) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19jSm6-00081t-00 for pf4freebsd@freelists.org; Mon, 04 Aug 2003 02:00:30 +0200 Message-ID: <001701c35a1b$9ac192e0$01000001@max900> From: "Max Laier" To: References: <20030803175508.67887.qmail@web12802.mail.yahoo.com> MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 61 X-ecartis-version: Ecartis v1.0.0 Sender: pf4freebsd-bounce@freelists.org Errors-To: pf4freebsd-bounce@freelists.org X-original-sender: max@love2party.net Precedence: normal X-list: pf4freebsd X-UID: 162 X-Length: 4294 X-Mailman-Approved-At: Thu, 16 Sep 2004 03:55:51 +0000 Subject: [pf4freebsd] Re: pf 1.59 and ALTQ install trouble X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.1 Reply-To: pf4freebsd@freelists.org List-Id: Technical discussion and general questions about packet filter (pf) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Thu, 16 Sep 2004 03:43:04 -0000 X-Original-Date: Mon, 4 Aug 2003 02:01:49 +0200 X-List-Received-Date: Thu, 16 Sep 2004 03:43:04 -0000 Hello, if you followed the instructions in README.ALTQ step by step (1-5) you created a directory "sys.altq" which holds the patched system source. If you now try to build the kernel "the new way" (which isn't really new, but more automated) you use the sources from sys *not* from sys.altq! That is why you don't have altq_* symbols in your kernel. If that wasn't the case (i.e. you patched in sys and did not create sys.altq) I am very interested to hear what else went wrong. Regards, Max > Hi again, > > yes, I understood all that; I now think my problem is that I'm building > and installing the kernel in the 'new' (and preferred, according to > FreeBSD) way and not the 'old' way. The PF instructions mention the > 'old' way for building/installing the kernel, but I figured I'd try the > 'new' way to see if it worked. I took both the PF and ALTQ > instructions and meshed them together, since section 5 in the PF > instructions is where it is outdated. Everything else is spot-on. > > I'm trying again with the 'old' method. I think the ALTQ (and PF) > instructions should explicitly state that the 'old' kernel > build/install method must be used. > > Which leads to my request that they be enhanced so that either the > 'old' or 'new' kernel method can be used. I haven't used the 'old' > method since about 4.6. Well, "step-by-step"-instructions are to be followed step-by-step. That is why we provide them as such. If you know what you are doing, you can build your kernel "the new way" (i.e. patch in sys not in sys.altq or modify the Makefile to reflect the change (good luck with that one ;)) > Build's about done. Time to verify. > > Thanks for the response and info. >