Date: Sun, 27 May 2018 21:12:17 +0200 From: Alexander Leidinger <Alexander@leidinger.net> To: freebsd-current@freebsd.org Subject: Re: Recent changes in routing or IPv6 related parts? Message-ID: <20180527211217.Horde.opQzHI4VOIxPiirx10J9wTe@webmail.leidinger.net> In-Reply-To: <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> References: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Quoting Chris H <bsd-lists@bsdforge.com> (from Tue, 22 May 2018 09:59:04 -0700): > On Tue, 22 May 2018 10:12:22 +0200 "Alexander Leidinger" > <Alexander@leidinger.net> said > >> Hi, >> >> I've updated 2 machines to r333966 and I see a change in the >> behavior in the network area on one of the systems. >> >> To begin with, the "original" behavior was not OK either, the em >> NIC fails to "do proper network communication" >> (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220997). A >> workaround for me was so far to do an IPv4 ping to the router from >> time to time, and if it fails do some ifconfig down/up. If the ping >> doesn't work afterwards, reboot. Most of the time this worked. >> >> Now I see a change in behavior, the scripts kicks in, all is ok for >> the script afterwards, but internally (inside the machine) I can't >> reach ipv6 jails. The system is reachable externally (only tested >> so far is the main host-IP). >> >> The setup is vimage based, several jails (via iocage) on epairs >> connected via bridge to the NIC. One bridge for IPv6, one for IPv4. >> rc.conf has prefer IPv4 setting after encountering another issue. >> >> One IPv4 address (/32) for the host where a nginx is running to >> proxy port 80 and 443 requests on IPv4 to the IPv6 addresses of >> the jails (IPv6 access is going directly to the jails). >> >> After a reboot, the nginx on the main IPv4 address delivers data >> from the ipv6 addresses of the jails (rev-proxy setup). After a >> while this stops working. The workaround-script mentioned above >> doesn't change this behavior. Restarting nginx doesn't help. A >> reboot helps. >> >> Has someone an idea of recent changes in a related area which may >> be able to cause such an issue? Any rev I could try to revert to >> check if it is related? > Hello, Alexander. > I'm not sure if this landed in -CURRENT. I only know it landed in 11. > But your trouble might be related to pr #224247 : > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224247 > > Hope this helps. Thanks, I've compiled a kernel which will print a message with the interface name when a packet will be dropped because of this. If I see something which makes it look like it could be related, I will disable it and try again. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbCwMRAAoJEKrxQhqFIICEF2EQALX7FSkUsisvL1+vbnH9rSFB PIkSb8YCapQpXscCeOgEbTGztnhI/jDMcFvMzOLr+f2Dy0z46MrgLPn/6pcmk52Q sBSu/rv24lUpgVD5kb1qAk9IhC8Pa7DU4CT23HAyXHP12h2UEdeQgFKS/mMc2Loi rD/E3r0qzgn5oIXvnW5qe231r+7Wmdstf1qoPThVETfA3RPhKV7CJa0BPnDYUcl4 OqB8u3AboButhHfSLgBUcas3OJdIrz3imUzQIbb8Mc0t1oo8qGALgxugsP+aEm6N 3rFW/Z8pUAn15/5E/sq5F96zG8lPde65uSBHH9zf4cNXRpDdgcmm9rUsFbcY9cY7 SPPL0HZm4xEsRe7hpLiTUcL6crOcnE6qkkV3noQpBWGmQhdVvcWIkytWd1Xdpu3Y RYaF4PCxn69jtUowEHbhp2mUNRhv1X0dsy4VUQ1r15liWFiH3hLrM45lv+GktI7j 9p/tlvsowL5ql/JPs1aKnAFX23HcOPEJHzKa2+X1qDTkWXoCK6wDb7TExNWKqVV0 aDTPrGkQbiFTecA1yJ0MhWhZCa36VhqjO1qx3YtcqGNim9c8unv65UwAKsYXXAyK C680MZs6jq5nvkokdMu0JY76jPuYPTBnqdlYCmL6/vYWqiXwuk46fhwxPEEoBwIU ssSQzZBX3IQixtjw10AI =JqqR -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180527211217.Horde.opQzHI4VOIxPiirx10J9wTe>