Date: Fri, 20 Mar 2020 22:03:17 -0700 From: Chris <bsd-lists@BSDforge.com> To: Victor Sudakov <vas@sibptus.ru> Cc: <freebsd-net@freebsd.org>, "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, Jan Behrens <jbe-mlist@magnetkern.de> Subject: Re: IPv6 in jails Message-ID: <16b9fef3ba2685ead7b5292d4d75c149@udns.ultimatedns.net> In-Reply-To: <20200321043502.GA51499@admin.sibptus.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 21 Mar 2020 11:35:02 +0700 Victor Sudakov vas@sibptus.ru said > Jan Behrens wrote: > > > > > Can you then do a jexec test4 and run service sshd restart and see if it > > > starts working? > > > > I experienced the same problem as discussed in this thread when I set > > up IPv6 with my server. 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. > > > > A "service sshd restart" inside the jail always seemed to help, which > > is why I also assumed there was some sort of race condition. But maybe > > it is related to some addresses being in use yet when restarting a jail? > > Does this happen only with IPv6 jail addresses? FWIW I never experience this on IP4, with some 7 jails starting simultaneously. But I'm also using pf, nat, and rdr. If that should that make a difference. --Chris > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49@fidonet http://vas.tomsk.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16b9fef3ba2685ead7b5292d4d75c149>