From owner-freebsd-questions@freebsd.org Tue Jun 18 14:41:23 2019 Return-Path: Delivered-To: freebsd-questions@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 88F9915BF2F1 for ; Tue, 18 Jun 2019 14:41:23 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84439807A0 for ; Tue, 18 Jun 2019 14:41:22 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr1-x429.google.com with SMTP id f9so14235782wre.12 for ; Tue, 18 Jun 2019 07:41:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=QXhOpyx9vuZQYLRJvmYl8iV0MnWD3qhwE5LCWa8w8eo=; b=p82Uj6eGEEeS8S9oIFq6OiPAn4GfiJY/KTXEAUWFV9gsVPsnfRHeTqzQrJbdcWVLQv 02m4tAjwXx+voikN6jD5u9JMqPJSo3Jboa3NI7H1mFrKEmiqA7i3/YB5mGe8kgogJy6i dQTr2MFtPCrY1tBVO3z5h8TYPrk5S7a6DyQX2q6VIOzBvRDKbV1XPLLm498jIuN9sYR7 sSZNghMuQ5jiChN4POviHonQnK5NXhjdhzSFbmlRAPqx1M5Yw9wH3Q6iV3CQCXQb9jjA sn3gTv++v9LQAowv+pz/AekcTQsd86o4opWkzmgWDyQbb95eVkqmoG3QB/0EpaeNw+qW yV5g== X-Gm-Message-State: APjAAAWFhqljWOpjw/21Dlr+Qb9GMLzzAl3OXrWJE4YHoDCwNmFQpEKL 3HeDcnKPOz5Yp6gV7/f/vZnbeYi5StuD7A== X-Google-Smtp-Source: APXvYqyPySY7x9f5i7E3ryEMG5YwZpHq9Ji9eWgWIgplJ5UC2quSM5TiyiT7/X9lM+UFbmPZnJ31dg== X-Received: by 2002:adf:a509:: with SMTP id i9mr72690015wrb.269.1560868881337; Tue, 18 Jun 2019 07:41:21 -0700 (PDT) Received: from gumby.homeunix.com ([2.121.228.92]) by smtp.gmail.com with ESMTPSA id a7sm14400828wrs.94.2019.06.18.07.41.19 for (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Tue, 18 Jun 2019 07:41:20 -0700 (PDT) Date: Tue, 18 Jun 2019 15:41:18 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Eliminating IPv6 (?) Message-ID: <20190618154118.45288c84@gumby.homeunix.com> In-Reply-To: <20190618150616.6ad64900@gumby.homeunix.com> References: <9AF5DF39-9B81-4270-B25C-D089C971E924@punkt.de> <19574.1560847186@segfault.tristatelogic.com> <23816.53518.998090.665606@jerusalem.litteratus.org> <20190618150616.6ad64900@gumby.homeunix.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 84439807A0 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.84 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; NEURAL_HAM_SHORT(-0.98)[-0.982,0]; RECEIVED_SPAMHAUS_PBL(0.00)[92.228.121.2.zen.spamhaus.org : 127.0.0.10]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; SUBJECT_HAS_QUESTION(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; RCVD_TLS_LAST(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; IP_SCORE(-2.85)[ip: (-9.36), ipnet: 2a00:1450::/32(-2.50), asn: 15169(-2.32), country: US(-0.06)]; RCVD_IN_DNSWL_NONE(0.00)[9.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2019 14:41:23 -0000 On Tue, 18 Jun 2019 15:06:16 +0100 RW wrote: > On Tue, 18 Jun 2019 14:35:00 +0200 > Patrick M. Hausen wrote: > > > Hi all, > > > > > Am 18.06.2019 um 13:54 schrieb Robert Huff : > > > > > > If this is true - haven't checked personally - then it's a > > > bug. (And a non-trivial one, the fact you're the first to report > > > it notwithstanding.) > > > Can you please open a bug report? > > > > I doubt it would qualify as a bug - possibly a bug in the docs, yes. > > > > Because the observed behaviour is definitely intentional. The flow > > of statements in rc.firewall is: > > > > 0. flush all rules > > 1. setup_loopback > > 2. setup_ipv6_mandatory > .. > > So, yes, there will always be mandatory IPv6 rules in place. > > The rules are only added if IPv6 is built into the kernel. > > It's a long time since I've used ipfw, but IIRC the custom file is > just a set of ipfw commands, so I presume it would be possible to > delete any unwanted preset rules without having to modify > rc.d/firewall. Looking at it again I see those rules are added in /etc/rc.firewall and the use of that script is optional in rc.d/ipfw, so there's no real problem in the first place. > Alternatively setup_loopback() starts with rule 100, so there is also > the option of adding custom rules that sort before the mandatory IPv6 > rules and override them.