Date: Sat, 31 Oct 2020 23:37:47 +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-bGLwDucSP5@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 Bjoern A. Zeeb <bz@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |In Progress CC| |hrs@FreeBSD.org --- Comment #22 from Bjoern A. Zeeb <bz@FreeBSD.org> --- Gert, can you try this patch (totally untested, not even compile tested): https://people.freebsd.org/~bz/tmp/20201031-02-ip6-ifdisabled.diff This will enable ND6_IFF_IFDISABLED when the interface is created in the ke= rnel before return to user space (if I am right) and user space (driver from dev= d -> /etc/pccard_ether =3D> ... netif start IF =3D> ifdisabled should no longer = execute the last bit and hence not race with your program. I might have seen a similar issue with ppp/tun0 lately. Also adding @hrs to Cc: as he know this logic a lot better than me and might know of other pitfalls by doing this. --=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-bGLwDucSP5>