From owner-freebsd-current@freebsd.org Thu Jan 31 07:35:34 2019 Return-Path: Delivered-To: freebsd-current@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 DA081134A60A; Thu, 31 Jan 2019 07:35:33 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D7FA37527C; Thu, 31 Jan 2019 07:35:32 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja ([79.192.175.91]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lx83d-1hDVP92Upt-016guK; Thu, 31 Jan 2019 08:35:30 +0100 Date: Thu, 31 Jan 2019 08:35:29 +0100 From: "O. Hartmann" To: "Andrey V. Elsukov" Cc: freebsd-current , jail@freebsd.org Subject: Re: icmp (IPv4) issues with VIMAGE JAILs and IPv6 Message-ID: <20190131083524.06555bc3@freyja> In-Reply-To: <8a6f74b5-f943-29de-2d65-88cf4e11e147@yandex.ru> References: <20190128134356.23a41e81@freyja> <8a6f74b5-f943-29de-2d65-88cf4e11e147@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:0CyjLB6SUv6NjBzfoEXlO2pkVrdcr96tIebXPU809dm5ltrW3za krE3nF1Mj1Y430cHGkmqZP0X6TEtzg47Kby9sWJM7dKgGyggQeu/+TusE6X3ZNLboTdfNvi 7rHmf935iZCckakTbn9wfrb4540cJOmolrTN4o1oHaLvn1cFmGqKk5ih8FM340mEbXipcaI fHKW1fAWqG7GDkMGsEQBw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:cGnShQrF9Cg=:J1FPwwhBPuY8LySNBwcOwJ GQFkJpaQ+V+emI3GKiHF6sQ5mTpWq2HemwKlZRk1flPT0ZxTGVPF6lCbzy4sQf8Elk0ty08z9 R8PeKbXtsBrNx1CfPalft0elbEIvN5sLlXBxUsBSCwt703d7y/zLpirW8HQ9pumFvbTouqqqW 6SsCwzjn8pbwg8GXwhJRku2/OLGrnY1xAu0Uykzhl+ToPVPRcLcWr469U73tSVu4TGc/x4VKw priGM/9pQkqDVOjF+2poK2u3bg0J471HDl3jq4uTBnVgkaOyNTCTRu+LcnU3hIKdoMy5pZM1w hAaGE2R3t6ReXMT5Vb27WOqOMU1ROqZ+vhZDvyN5YcFmgLPDk5uTUoODsQ9DIjhLtd0fx4GPF wk4bVP57M7KqAyWaR+JftyLZswCVmYuEGtqN9Q75xhvfXI+lx+rTRRVuirOFD0g+37yuDNI5s OqUoBEvBPv7n3QDIvaYA6YIPpwynDyknhNB94M2f24bMYjWpJ6+sfRdkvVZ9xITaf7+KDLZpm HwKV/c2xG7/GywKb//80JjVD624O0T/hjlKqfBzvUGDK4p0Hu2M8n+FjnIqVU3x0YHwiljfcb wwjpEKekRazRdyWfmDeI8q+ZHYYanSS1FZDa0KbNSmjUOsgkCz6K8y6avsoCBTubujr1Q4W2f iVy9NdL9BTwAJcuR6BGEJeqcQZxCEMuXyDUeAzONiGXa+6SAV6xaKARvqCVp8rnwMI1AnQedT SQYl04mGAINWYUbcX7kQ5Q9c9lWNOayAn2zU+tHyGA5maBMWprHJv7OcSmNbWxzvn1Qd4xS2D kIztHp0v/iTciZJ9sXc0K+lQfeh2s4agHUG1FnfJHfvKgvKy/lIJeOvdP9qTCYBrSBd8JbraF Mqq3eK/JpkRUVLJb618LeKB4lLPMYGOx+cEuuJoI3uxF+MMZzqIbBlb5u+y2+e7Hw4uQPZbVR /bTQi+caMCA== X-Rspamd-Queue-Id: D7FA37527C X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [1.69 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; MX_GOOD(-0.01)[cached: mx01.gmx.net]; FREEMAIL_TO(0.00)[yandex.ru]; RECEIVED_SPAMHAUS_PBL(0.00)[91.175.192.79.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; IP_SCORE(-0.34)[ip: (-3.07), ipnet: 212.227.0.0/16(-0.73), asn: 8560(2.11), country: DE(-0.01)]; RCVD_IN_DNSWL_LOW(-0.10)[15.15.227.212.list.dnswl.org : 127.0.3.1]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.53)[0.532,0]; NEURAL_HAM_LONG(-0.58)[-0.585,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[walstatt.org]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.79)[0.787,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2019 07:35:34 -0000 On Tue, 29 Jan 2019 11:36:37 +0300 "Andrey V. Elsukov" wrote: > On 28.01.2019 15:44, O. Hartmann wrote: > > 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 anyone have any ideas? I'm out of ideas. > > Hi, > > I think I found the problem, the bug was introduced in r342908. > Can you try attached patch? > Sorry for responding so late. Thank you for digging into this problem - and finally having resolved it! Great. After the patch has been apllied, the system worked as expected. Thanks a lot. Regards, Oliver