From owner-freebsd-pf@FreeBSD.ORG Wed Mar 2 19:12:54 2005 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 DB10216A4CE for ; Wed, 2 Mar 2005 19:12:54 +0000 (GMT) Received: from post2.wesleyan.edu (post2.wesleyan.edu [129.133.6.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id 287FA43D2D for ; Wed, 2 Mar 2005 19:12:54 +0000 (GMT) (envelope-from vsavichev@wesleyan.edu) Received: from localhost.localdomain (pony3.wesleyan.edu [129.133.6.194]) by post2.wesleyan.edu (8.12.11/8.12.11) with ESMTP id j22JCo3b007577 for ; Wed, 2 Mar 2005 14:12:50 -0500 Received: from localhost.localdomain (pony3 [127.0.0.1]) j22JCoeq018432 for ; Wed, 2 Mar 2005 14:12:50 -0500 Received: (from apache@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id j22JCoGs018430; Wed, 2 Mar 2005 14:12:50 -0500 Received: from 81.30.200.207 (SquirrelMail authenticated user vsavichev); by webmail.wesleyan.edu with HTTP; Wed, 2 Mar 2005 14:12:50 -0500 (EST) Message-ID: <57056.81.30.200.207.1109790770.squirrel@81.30.200.207> Date: Wed, 2 Mar 2005 14:12:50 -0500 (EST) From: vsavichev@wesleyan.edu To: freebsd-pf@freebsd.org User-Agent: SquirrelMail/1.4.3a-0.e3.1 X-Mailer: SquirrelMail/1.4.3a-0.e3.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Wesleyan-MailScanner-Information: Please contact the ISP for more information X-Wesleyan-MailScanner: Found to be clean X-MailScanner-From: vsavichev@wesleyan.edu Subject: pfsync + pfflowd + flow-tools (ifconfig maxupd)? 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: Wed, 02 Mar 2005 19:12:55 -0000 hi all, we're trying to build pfsync centric accounting system. Our plan is to use pfflowd to emit NetFlow datagrams to work them out within flow-tools. E.g., using flow-receive we get SOMEFILE which can be further proceesed by flow-export or alikes. We found that SOMEFILE gets occassionaly updated. man pfsync says that state infomation refreshment is condensed which is controled by maxupd parameter to ifconfig (equal by default to 128). For some reason FreeBSD (5.3-stable) version of ifconfig has no maxupd option, OpenBSD does. So we believe now, pfsync iface in that incarnation of FreeBSD has no way to change this parameter and hence to fine tune state information update frequency. Is that so? Vlad