From owner-freebsd-current@freebsd.org Tue May 22 11:52:10 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 0D56EEF28BF for ; Tue, 22 May 2018 11:52:10 +0000 (UTC) (envelope-from Alexander@leidinger.net) 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 817377095B for ; Tue, 22 May 2018 11:52:09 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: by mailman.ysv.freebsd.org (Postfix) id 410FEEF28BE; Tue, 22 May 2018 11:52:09 +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 19793EF28BD for ; Tue, 22 May 2018 11:52:09 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9790470952 for ; Tue, 22 May 2018 11:52:07 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Tue, 22 May 2018 10:12:22 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1526989920; bh=WU9TZfXctqAagUEWAuYiTxfkgaZt2ywrwls69JRDCdE=; h=Date:From:To:Subject; b=YxIFxfxMLsC+1ShvvkMe1DBOZgz/XFHnLjZhP71eIWwaryMVD/VT8ytr8ofc9ap/C n9gh+zMdjpJx12sWyWwqZ14MK6+6+bKZJhZTt94YkSKO++2iIpc/cSqQ1IaJqdIDNb ItwIwkTV/K7CaZos/Sw94LeZbHH6K6wCa9WUu8ZLEicp+VWsnd0wxbFKMsYsa+l5DZ NStNTKQpm35zpTqQ/5BCzuHZL5EKHj7PsxfJNQCc2CdQNutkc53t7V6/j5Z9EF27IN l+JvEVtRjxDdkcisfdXhRvSKUp0F8O3Vjz+qnIM+YaKJBmBGsDDrsRb/I9sba8mhno UwpMjpwRenCeA== Message-ID: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> From: Alexander Leidinger To: current@freebsd.org Subject: Recent changes in routing or IPv6 related parts? User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_k8eHYbkqlkqmDMHKlZ3_Yev"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 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 11:52:10 -0000 This message is in MIME format and has been PGP signed. --=_k8eHYbkqlkqmDMHKlZ3_Yev Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've updated 2 machines to r333966 and I see a change in the behavior=20=20 in=20the network area on one of the systems. To begin with, the "original" behavior was not OK either, the em NIC=20=20 fails=20to "do proper network communication"=20=20 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220997). A=20=20 workaround=20for me was so far to do an IPv4 ping to the router from=20=20 time=20to time, and if it fails do some ifconfig down/up. If the ping=20=20 doesn't=20work afterwards, reboot. Most of the time this worked. Now I see a change in behavior, the scripts kicks in, all is ok for=20=20 the=20script afterwards, but internally (inside the machine) I can't=20=20 reach=20ipv6 jails. The system is reachable externally (only tested so=20= =20 far=20is the main host-IP). The setup is vimage based, several jails (via iocage) on epairs=20=20 connected=20via bridge to the NIC. One bridge for IPv6, one for IPv4.=20=20 rc.conf=20has prefer IPv4 setting after encountering another issue. One IPv4 address (/32) for the host where a nginx is running to proxy=20=20 port=2080 and 443 requests on IPv4 to the IPv6 addresses of the jails=20=20 (IPv6=20access is going directly to the jails). After a reboot, the nginx on the main IPv4 address delivers data from=20=20 the=20ipv6 addresses of the jails (rev-proxy setup). After a while this=20= =20 stops=20working. The workaround-script mentioned above doesn't change=20=20 this=20behavior. Restarting nginx doesn't help. A reboot helps. Has someone an idea of recent changes in a related area which may be=20=20 able=20to cause such an issue? Any rev I could try to revert to check if=20= =20 it=20is related? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_k8eHYbkqlkqmDMHKlZ3_Yev Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbA9DlAAoJEKrxQhqFIICESiwQAI841duaYjJPyAvSnYgoXsVd 1uv82HFCQsV2/1zENVqREV4EpqxqOqSJnTZT5udAfnRj4728oaOQUOxwtRNwVLRO o89WrY9WpwLoLh9RjxTA01dZqSZfjSoMjyP+QX0TDckmy0RCWjbSExsPEiYaGvwZ gMZYPKHCiheiJMCdz+RU0wm2FQzbP5UQIoD+oE3ym4Kf0OxGRHaMg8eGOUZKYtkX ttPnzNgesInW4LKx0fFPp46ZUo/LufV6GCjR1UQjk0+iWCbW2PaUb8HbXpEMv0Fr C3wBcvF76r6UeLT9FcaYUsmLGDewGVnxmK+3NR+fShoRJWlIR3HsxbnlXYDd4BnX tYh/0Xbo2AoAUc5qwS6W+gP5Cl3Yw0DIfcmC6/Fryt7Ou+phPiK51njNYWtEzHEu 21qhBqV9IwL0lqHufPi8bQ6V2tyOuwCrxwSLFUGLCVro9wD7j0CCXwwpe/8/3S+y UuCgCjlaW2iMzi/Lm2KMm9uofRfdlUQe5/W8rtTFUVrvQyXzuq/ZssvGaP4Nkuih rqhfBKC5M+/Qm8UJKxhJq8lMrmEQ6KHBOuGVq/0RETZlxVqOFRfwSujww5ro0yCA MAKvDhOo7t9z859xdfHZts0MwoOuUJSU5/nzRPXDaiZPeeZxWgNewWcNHkXGRVaQ FiHe4wJRIegarHH+pt2t =GAZ+ -----END PGP SIGNATURE----- --=_k8eHYbkqlkqmDMHKlZ3_Yev--