From owner-freebsd-ipfw@FreeBSD.ORG Thu Jul 26 05:34:54 2012 Return-Path: Delivered-To: ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBD2F106566B; Thu, 26 Jul 2012 05:34:54 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id 8DD158FC08; Thu, 26 Jul 2012 05:34:54 +0000 (UTC) Received: from JRE-MBP-2.local (c-67-180-24-15.hsd1.ca.comcast.net [67.180.24.15]) (authenticated bits=0) by vps1.elischer.org (8.14.5/8.14.5) with ESMTP id q6Q5Yic0048033 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 25 Jul 2012 22:34:46 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <5010D6EF.9040805@freebsd.org> Date: Wed, 25 Jul 2012 22:34:39 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Luigi Rizzo References: <20120725184104.GA35621@onelab2.iet.unipi.it> In-Reply-To: <20120725184104.GA35621@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ipfw@freebsd.org, net@freebsd.org Subject: Re: PREVIEW - netmap-enabled ipfw X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2012 05:34:54 -0000 On 7/25/12 11:41 AM, Luigi Rizzo wrote: > First and foremost: this is just a preview, only usable for testing now, > but very very close to working. > > http://info.iet.unipi.it/~luigi/netmap/20120725-ipfw-user.tgz > > [...] > connected to 127.0.0.1:5555 > 00100 30628621 1408916566 count ip from any to any dst-ip 10.1.0.1 > 00100 0 0 count ip from any to any dst-ip 10.1.0.2 > 00100 0 0 count ip from any to any dst-ip 10.1.0.3 > 65535 30628621 1408916566 allow ip from any to any how do you handle rules that require to be able to see routes and socket owners?