Date: Sun, 04 Apr 2021 19:13:01 +0000 From: bugzilla-noreply@freebsd.org To: ipfw@FreeBSD.org Subject: [Bug 160206] [gif] gifX stops working after a while (IPv6 tunnel) Message-ID: <bug-160206-8303-e0IXH3BvTS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-160206-8303@https.bugs.freebsd.org/bugzilla/> References: <bug-160206-8303@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D160206 --- Comment #8 from Paul Scott <pscott@skycoast.us> --- It may not be specific to IPFW, after all, although IPFW does seem to exacerbate the problem. Recently, I've noticed that the FreeBSD 12.2-RELEASE-p1 GENERIC (and64) dro= plet has had issues with both ICMP and ssh over IPv6. The following occurs even with IPFW disabled: ICMPv6 and ssh -6 setup are working fine, and then suddenly they stop worki= ng. When this happens, a ping6 will never succeed no longer how long it runs, a= nd an ssh -6 will ultimately fail. If I interrupt (Ctrl-C) the process and try again it MAY immediately start working and continue to work indefinitely. Curiously, I can have two ping6 processes running simultaneously and one wi= ll indefinitely fail and the other will indefinitely succeed. When ssh -6 setup succeeds the session will remain responsive indefinitely without any failure even if another ssh -6 setup fails simultaneously. Note that IPv4 experienced none of these issues. Further, this isn't a DNS failure since the name is properly resolved, and using an IP address instea= d of a name produces the same results. CentOS linux systems in the same data center location experience none of th= ese problems and IPv6 is 100% reliable there. The FreeBSD droplets all experien= ce the problem, however. Given that a non-FreeBSD OS in the same data center has none of these probl= ems and that other people -- witnessed by this PR and quite a few google search results -- have had similar IPv6 issues on FreeBSD over various network adapters, it's extremely likely this is a FreeBSD or FreeBSD subsystem defe= ct. I was hoping to move all my systems from CentOS to FreeBSD but these IPv6 issues will, sadly, prevent me from making that transition. If there is anything I can do to help bring about a resolution quickly, ple= ase let me know. Unfortunately, as this problem has a long history, on the orde= r of years, I'm not hopeful it will get solved soon. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-160206-8303-e0IXH3BvTS>