From owner-freebsd-ipfw@freebsd.org Wed Oct 24 18:44:12 2018 Return-Path: Delivered-To: freebsd-ipfw@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9765F10366DC for ; Wed, 24 Oct 2018 18:44:12 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward103p.mail.yandex.net (forward103p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F310874E07 for ; Wed, 24 Oct 2018 18:44:11 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback15o.mail.yandex.net (mxback15o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::66]) by forward103p.mail.yandex.net (Yandex) with ESMTP id C10792183FEA; Wed, 24 Oct 2018 21:43:47 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback15o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 8KcNkyRQz0-hlG0FBrd; Wed, 24 Oct 2018 21:43:47 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1540406627; bh=KVK0DICFBhmuRt9LmPMyyYV+kRpZFN+xjipvsUGymFA=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=LVaAS4hCv7alUiaFKEV4i0hxrFKF/zboe62Q3e+ngdZumEzUWKneEBFdmEb6KF+/C H7sSZ5gyttyIULCl1kYsUOD61SrB3auPpdTnnQo0yfXJbYQ7gSpOH/kp0u5z4zn7JF 9iIOS/B9Tjb4DdY4E5KQO2hG8E3/qGYMHBCJuqrM= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 710xxvbPLD-hkn4LvCr; Wed, 24 Oct 2018 21:43:46 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1540406626; bh=KVK0DICFBhmuRt9LmPMyyYV+kRpZFN+xjipvsUGymFA=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=f5pq8ttxj+oOHGLaa2Qjt5nsGLSngP2EuNiyr1t6hRe4AhD3bYMIfOc8K7zUIfHlM FNSKpF63PwIwAwgBjHc/kZbk5fY7M8Cfp3Vn8AxQeM9BFlW+mRxCPYffYcT4P4ZVZ2 nb2dsFR2CBURgoTqfsE18PoX7IlzfuV5GNiRQv/E= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: ipfw managing rules - best practice? To: Ole Cc: freebsd-ipfw@freebsd.org References: <20180905112847.54287198.ole@free.de> <67544958-07fe-7ff4-b5d2-88bf85324061@yandex.ru> <20181023131220.20c700ba.ole@free.de> <20181024182252.49ee516b.ole@free.de> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= xsBNBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAHNIkFuZHJleSBWLiBFbHN1a292IDxhZUBmcmVlYnNkLm9yZz7CwHsEEwECACUCGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheABQJMB/ruAhkBAAoJEAHF6gQQyKF6MLwH/3Ri/TZl9uo0 SepYWXOnxL6EaDVXDA+dLb1eLKC4PRBBjX29ttQ0KaWapiE6y5/AfzOPmRtHLrHYHjd/aiHX GMLHcYRXD+5GvdkK8iMALrZ28X0JXyuuZa8rAxWIWmCbYHNSBy2unqWgTI04Erodk90IALgM 9JeHN9sFqTM6zalrMnTzlcmel4kcjT3lyYw3vOKgoYLtsLhKZSbJoVVVlvRlGBpHFJI5AoYJ SyfXoN0rcX6k9X7Isp2K50YjqxV4v78xluh1puhwZyC0p8IShPrmrp9Oy9JkMX90o6UAXdGU KfdExJuGJfUZOFBTtNIMNIAKfMTjhpRhxONIr0emxxDOwE0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAcLAXwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: <6bb037c2-643d-151b-cb34-f78c97f241d4@yandex.ru> Date: Wed, 24 Oct 2018 21:42:00 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181024182252.49ee516b.ole@free.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xTkE80mW3ce0SYYNyUoFX9oEw4CeS3ICF" X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 18:44:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xTkE80mW3ce0SYYNyUoFX9oEw4CeS3ICF Content-Type: multipart/mixed; boundary="LBxTwxfGlYY1I14vTXF3iQdZhxqGK7ymm"; protected-headers="v1" From: "Andrey V. Elsukov" To: Ole Cc: freebsd-ipfw@freebsd.org Message-ID: <6bb037c2-643d-151b-cb34-f78c97f241d4@yandex.ru> Subject: Re: ipfw managing rules - best practice? References: <20180905112847.54287198.ole@free.de> <67544958-07fe-7ff4-b5d2-88bf85324061@yandex.ru> <20181023131220.20c700ba.ole@free.de> <20181024182252.49ee516b.ole@free.de> In-Reply-To: <20181024182252.49ee516b.ole@free.de> --LBxTwxfGlYY1I14vTXF3iQdZhxqGK7ymm Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 24.10.2018 19:22, Ole wrote: > # ipfw -d list=20 > (...) > 01510 allow tcp from any to xx.xx.xx.xx 6514 out via epair0b setup keep= -state :default > (...) > ## Dynamic rules (1 152): > 01510 STATE tcp yy.yy.yy.yy 54451 <-> xx.xx.xx.xx 6514 :default >=20 > # ipfw -q flush >=20 > # ipfw -d list > 65535 allow ip from any to any > ## Dynamic rules (2 288): > Segmentation fault (core dumped) This problem is related to named states, the kernel doesn't dump list of known states names, and this is the cause of SIGSEGV. I have the WIP patch https://people.freebsd.org/~ae/keep_states.diff It fixes this problem and also add support for all rule actions. Also it adds new -D flag, that allows to show only states and delete only states. I have tested it basically, but it probably needs some work related to "limit" dynamic states. So if you want to test some patches, you can try :) I tried to apply the patch and observed that stable/11 has a small difference in UMA code, so you need to use this patch: https://people.freebsd.org/~ae/keep_states11.diff Again, I did not yet teseted it widely, and on stable/11 did not tested at all. --=20 WBR, Andrey V. Elsukov --LBxTwxfGlYY1I14vTXF3iQdZhxqGK7ymm-- --xTkE80mW3ce0SYYNyUoFX9oEw4CeS3ICF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlvQvPgACgkQAcXqBBDI oXo2AQgAkpx86MReoTBlhDctC9KtqKZs2wQlQFZtL/IfGvbj/ZAv0oX2c4UADCJz 3I2OKQC9Lziem4MimZrsEjgbLpPbQ5H0EU5O1vJ0tsKJfRq14VeaHYEHTKPpUzjn WGrsWxd5luWov6VIPf60QUJnkdJk+7Q6mefao7M1OueD3ipnVMA8u6/YbPPf/nWc TKVnvxURftX547KhWR5zQ2WE5OO2ADyoWxjnP4qFrtkodO77w3yWtjqqCQpWBPhl jklxyooWbH/m+Hs7whp7URNweJCUDco+9X4oE7NG3VAWWZb/7GATrKdOaAgtBzXp 9HSB8AO+ExI5LGTPG0g8epujAc3lzg== =aHFV -----END PGP SIGNATURE----- --xTkE80mW3ce0SYYNyUoFX9oEw4CeS3ICF--