From owner-freebsd-net@freebsd.org  Sat Mar 21 05:02:54 2020
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7602F27EF6C
 for <freebsd-net@mailman.nyi.freebsd.org>;
 Sat, 21 Mar 2020 05:02:54 +0000 (UTC)
 (envelope-from bsd-lists@BSDforge.com)
Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com
 [24.113.41.81])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "ultimatedns.net",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 48kpRx6cC5z4DkF
 for <freebsd-net@freebsd.org>; Sat, 21 Mar 2020 05:02:53 +0000 (UTC)
 (envelope-from bsd-lists@BSDforge.com)
Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1])
 by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 02L53Bwt084749
 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO);
 Fri, 20 Mar 2020 22:03:17 -0700 (PDT)
 (envelope-from bsd-lists@BSDforge.com)
X-Mailer: Cypht
MIME-Version: 1.0
Cc: <freebsd-net@freebsd.org>,
 "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>,
 Jan Behrens <jbe-mlist@magnetkern.de>
In-Reply-To: <20200321043502.GA51499@admin.sibptus.ru>
From: Chris <bsd-lists@BSDforge.com>
Reply-To: bsd-lists@BSDforge.com
To: Victor Sudakov <vas@sibptus.ru>
Subject: Re: IPv6 in jails
Date: Fri, 20 Mar 2020 22:03:17 -0700
Message-Id: <16b9fef3ba2685ead7b5292d4d75c149@udns.ultimatedns.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Rspamd-Queue-Id: 48kpRx6cC5z4DkF
X-Spamd-Bar: +
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [1.92 / 15.00]; NEURAL_SPAM_LONG(0.99)[0.986,0];
 NEURAL_SPAM_MEDIUM(0.93)[0.935,0];
 ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US];
 local_wl_ip(0.00)[24.113.41.81]
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2020 05:02:54 -0000

On Sat, 21 Mar 2020 11:35:02 +0700 Victor Sudakov vas@sibptus=2Eru said

> Jan Behrens wrote:
> >=20
> > > Can you then do a jexec test4 and run service sshd restart and see if=
 it=20
> > > starts working?
> >=20
> > I experienced the same problem as discussed in this thread when I set
> > up IPv6 with my server=2E Strangely, when I rebooted the host system and
> > simply started the jails one after the other (with a freshly booted
> > host system), the problem didn't occur, but maybe that was just random=2E
> >=20
> > A "service sshd restart" inside the jail always seemed to help, which
> > is why I also assumed there was some sort of race condition=2E But maybe
> > it is related to some addresses being in use yet when restarting a jail=
?
>=20
> Does this happen only with IPv6 jail addresses?
FWIW I never experience this on IP4, with some 7 jails starting simultaneou=
sly=2E
But I'm also using pf, nat, and rdr=2E If that should that make a difference=2E

--Chris
>=20
> --=20
> Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
> 2:5005/49@fidonet http://vas=2Etomsk=2Eru/