From owner-freebsd-net@FreeBSD.ORG Tue May 13 12:06:01 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 44E9EBCF for ; Tue, 13 May 2014 12:06:01 +0000 (UTC) Received: from quix.smartspb.net (quix.smartspb.net [217.119.16.133]) (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 F3E212F10 for ; Tue, 13 May 2014 12:05:59 +0000 (UTC) Received: from dyr.smartspb.net ([217.119.16.26] helo=[127.0.0.1]) by quix.smartspb.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.61 (FreeBSD)) (envelope-from ) id 1WkBW1-000F6D-HD for freebsd-net@freebsd.org; Tue, 13 May 2014 16:09:01 +0400 Message-ID: <53720AA4.80909@smartspb.net> Date: Tue, 13 May 2014 16:05:56 +0400 From: Dennis Yusupoff User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: FreeBSD Net Subject: Re: 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> In-Reply-To: <5371F4C8.3080501@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 140512-4, 12.05.2014), Outbound message X-Antivirus-Status: Clean 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, 13 May 2014 12:06:01 -0000 I think that universal table for all kind of data (ipv4, ipv6, ports, etc) is a bad idea by design. At least unless you haven't any ability to specify address family on add, to avoid attempts to guess what user meant. Something like "ipfw table X add DEEF.DE ipv6". 13.05.2014 14:32, Alexander V. Chernikov пишет: > On 13.05.2014 13:46, Dennis Yusupoff wrote: >> May be this will help? See answer on >> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/189471 > I'll try to fix it within a few days. > > The problem itself happens due to the fact that every CIDR table > address is packed into IPv6 address and IPv4 ones are encoded as > deprecated IPv6-compatible ones. > this leads to the problems with decoding things like 0/X or ::1 -- Best regards, Dennis Yusupoff, network engineer of Smart-Telecom ISP Russia, Saint-Petersburg