Date: Wed, 22 Jul 2020 14:15:53 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces Message-ID: <bug-248172-7501-xZBPFTINbi@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/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #4 from Gert Doering <gert@greenie.muc.de> --- Hi, thanks for your quick replies. A few answers right away: - Exact freebsd versions affected (uname -a) FreeBSD fbsd-tc.ov.greenie.net 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 GENERIC amd64 - Minimum network configuration necessary to reproduce (/etc/rc.conf, openvpn or pure tun/tap config (ideally)) Sharing the actual OpenVPN config is complicated (the config is very simple, but it's part of our CI tests, so without "the other end" it won't do much) - truss or similar trace output under reproduction (as an attachment) - /var/run/dmesg.boot output (as an attachment) - confirmation whether openvpn/openvpn-devel from ports/packages also exhibits this issue. Right now, my system is stubbornly refusing to show the effect at all - but if it does so, the effect is the same for openvpn (2.4.x) or openvpn-devel (which is our git master state as of two days ago, with no FreeBSD specific patches). While it nicely did this for "80%" of the cases beforehand... I think the easiest way is to write a test program, which I'll do tonight and attach it. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-248172-7501-xZBPFTINbi>