From owner-freebsd-ipfw@freebsd.org Mon Jan 28 13:42:38 2019 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 D2CB814B475C; Mon, 28 Jan 2019 13:42:38 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 68D678C9E3; Mon, 28 Jan 2019 13:42:38 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id A4B158D4A142; Mon, 28 Jan 2019 13:42:28 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 3AD24D21CE1; Mon, 28 Jan 2019 13:42:27 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 2C21gqIVXA5z; Mon, 28 Jan 2019 13:42:25 +0000 (UTC) Received: from [192.168.2.110] (unknown [IPv6:fde9:577b:c1a9:31:2ef0:eeff:fe03:ee34]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 7D441D21CDF; Mon, 28 Jan 2019 13:42:25 +0000 (UTC) From: "Bjoern A. Zeeb" To: "O. Hartmann" Cc: freebsd-current , jail@freebsd.org, freebsd-ipfw@freebsd.org Subject: Re: icmp (IPv4) issues with VIMAGE JAILs and IPv6 Date: Mon, 28 Jan 2019 13:42:24 +0000 Reply-To: freebsd-ipfw@freebsd.org X-Mailer: MailMate (2.0BETAr6135) Message-ID: <685AA96F-4E00-444E-972A-384D30683495@lists.zabbadoz.net> In-Reply-To: <20190128134356.23a41e81@freyja> References: <20190128134356.23a41e81@freyja> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 68D678C9E3 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.97)[-0.973,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] 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: Mon, 28 Jan 2019 13:42:39 -0000 On 28 Jan 2019, at 12:44, O. Hartmann wrote: > I ran into severe problems on CURRENT ( FreeBSD 13.0-CURRENT #193 > r343521: Mon Jan 28 10:26:36 CET 2019 amd64), VIMAGE enabled host with > jails > utilizing IPv6. and you forget to mention in the subject that it seems to be an ipfw problem and thus missing your target audience most likely. > Stopping all jails, destroying all epairs and bridge0 doesn't change > anything. > > The problems occured when IPv6 came into play on the specific host in > question. Does that mean you could reproduce the problem just with bce0 and no jail+vnets at all just with IPv4, IPv6, and ipfw on the main host? If you cannot, would starting a vnet-jail (without the bridge and connecting the epair), just starting a jail in persist mode, make a difference; or would strating a jail and applying the ipfw rules therein start the problem? > Does anyone have any ideas? I'm out of ideas. y best guess is to move the thread to freebsd-ipfw (Cc: and Reply-To: set) and see if people pick it up there some more and also finding the minimalistic case to reproduce. /bz