From owner-freebsd-current@freebsd.org Tue May 22 16:56:14 2018 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 2B0EBEFC85F for ; Tue, 22 May 2018 16:56:14 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id B267A7FE5C for ; Tue, 22 May 2018 16:56:13 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: by mailman.ysv.freebsd.org (Postfix) id 72F70EFC85A; Tue, 22 May 2018 16:56:13 +0000 (UTC) Delivered-To: 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 5EB8CEFC859 for ; Tue, 22 May 2018 16:56:13 +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 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D769B7FE5B for ; Tue, 22 May 2018 16:56:12 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w4MGwwcs056947; Tue, 22 May 2018 09:59:04 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: In-Reply-To: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Alexander Leidinger" Subject: Re: Recent changes in routing or IPv6 related parts? Date: Tue, 22 May 2018 09:59:04 -0700 Message-Id: <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Tue, 22 May 2018 16:56:14 -0000 On Tue, 22 May 2018 10:12:22 +0200 "Alexander Leidinger" said > Hi, >=20 > I've updated 2 machines to r333966 and I see a change in the behavior =20 > in the network area on one of the systems=2E >=20 > To begin with, the "original" behavior was not OK either, the em NIC =20 > fails to "do proper network communication" =20 > (https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D220997)=2E A =20 > workaround for me was so far to do an IPv4 ping to the router from =20 > time to time, and if it fails do some ifconfig down/up=2E If the ping =20 > doesn't work afterwards, reboot=2E Most of the time this worked=2E >=20 > Now I see a change in behavior, the scripts kicks in, all is ok for =20 > the script afterwards, but internally (inside the machine) I can't =20 > reach ipv6 jails=2E The system is reachable externally (only tested so =20 > far is the main host-IP)=2E >=20 > The setup is vimage based, several jails (via iocage) on epairs =20 > connected via bridge to the NIC=2E One bridge for IPv6, one for IPv4=2E =20 > rc=2Econf has prefer IPv4 setting after encountering another issue=2E >=20 > One IPv4 address (/32) for the host where a nginx is running to proxy =20 > port 80 and 443 requests on IPv4 to the IPv6 addresses of the jails =20 > (IPv6 access is going directly to the jails)=2E >=20 > After a reboot, the nginx on the main IPv4 address delivers data from =20 > the ipv6 addresses of the jails (rev-proxy setup)=2E After a while this =20 > stops working=2E The workaround-script mentioned above doesn't change =20 > this behavior=2E Restarting nginx doesn't help=2E A reboot helps=2E >=20 > Has someone an idea of recent changes in a related area which may be =20 > able to cause such an issue? Any rev I could try to revert to check if = =20 > it is related? Hello, Alexander=2E I'm not sure if this landed in -CURRENT=2E I only know it landed in 11=2E But your trouble might be related to pr #224247 : https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D224247 Hope this helps=2E --Chris >=20 > Bye, > Alexander=2E >=20 > --=20 > http://www=2ELeidinger=2Enet Alexander@Leidinger=2Enet: PGP 0x8F31830F9F2772BF > http://www=2EFreeBSD=2Eorg netchild@FreeBSD=2Eorg : PGP 0x8F31830F9F2772BF