Date: Thu, 23 Jul 2020 09:13:33 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 248172] if_tuntap(4): OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces Message-ID: <bug-248172-7501-V8IFsWfRSU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-248172-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-248172-7501@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=3D248172 --- Comment #14 from Gert Doering <gert@greenie.muc.de> --- (In reply to Andrey V. Elsukov from comment #12) rc.conf settings can not be the correct answer for spurious and timing-dependent differences in behaviour. Also, I can not control what our users will do (and they might not have IPv= 6 on the LAN side, so might not have turned it on in rc.conf) - so I need a reli= able and robust way to bring up a tunnel interface with IPv6, independent of rc.= conf settings. Adding some argument to our ifconfig call (or adding some extra ioctl()s or whatever) is not a problem, but right now I need an extra "sleep(1)" before= the "ifconfig $dev inet6 -ifdisable", which looks race'y and probably is... --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248172-7501-V8IFsWfRSU>