From owner-freebsd-net@FreeBSD.ORG Tue May 20 17:34:28 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 14344F4E for ; Tue, 20 May 2014 17:34:28 +0000 (UTC) Received: from mail.ipfw.ru (mail.ipfw.ru [IPv6:2a01:4f8:120:6141::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C684B2D70 for ; Tue, 20 May 2014 17:34:27 +0000 (UTC) Received: from 95.108.170.210-red.dhcp.yndx.net ([95.108.170.210] helo=ptichko.yndx.net) by mail.ipfw.ru with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from ) id 1Wmk1T-0002Yk-B5 for freebsd-net@freebsd.org; Tue, 20 May 2014 17:24:03 +0400 Message-ID: <537B91C2.7000609@FreeBSD.org> Date: Tue, 20 May 2014 21:32:50 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: [Was]: Problem with ipfw table add 0.0.0.0/8 References: <5371084F.1060009@bsdinfo.com.br> <5371112B.2030209@bsdinfo.com.br> <5371E9E7.70400@smartspb.net> <5371F4C8.3080501@FreeBSD.org> <53720AA4.80909@smartspb.net> <537767C5.80205@FreeBSD.org> <53783333.3010205@freebsd.org> <5379C6B6.4030105@smartspb.net> <537A00AC.6050305@FreeBSD.org> <537A0560.2070902@gmail.com> <537A0967.1000808@smartspb.net> In-Reply-To: <537A0967.1000808@smartspb.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 17:34:28 -0000 On 19.05.2014 17:38, Dennis Yusupoff wrote: > It's not enough, actually. > Imagine what you have a table with different networks. If you'll try to > find out is an IP belongs to some of that networks from the table, you > should to write relatively serious "wrapper" with network range > calculations in it. Or can you show differ (easier) way? > So it's REALLY usefull to implement that functions "out-of-the-box". Doing "test" function is quite easy. I'll probably do this after finishing new tables code merge. > I'm risking to be annoying, but there is a good (from customers point of > view) example of tables manipulation in Linux: ipset project > (http://ipset.netfilter.org/ipset.man.html) > > 19.05.2014 17:21, bycn82 пишет: >> It will be nice to have this feature, >> but since the `ipfw table list` is existing, >> so I think this can be implemented outside the ipfw. >> (personal opinion only ) >> >