[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
           Keywords|                            |needs-qa, regression
           Severity|Affects Only Me             |Affects Some People
              Flags|                            |mfc-stable12?
           Assignee|bugs at FreeBSD.org            |net at FreeBSD.org
            Summary|OpenVPN configuring tun/tap |tun/tap: OpenVPN
                   |devices ends up with        |configuring tun/tap devices
                   |IFDISABLED interfacs        |ends up with IFDISABLED
                   |                            |interfaces
                 CC|                            |mandree at FreeBSD.org,
                   |                            |net at FreeBSD.org

--- Comment #1 from Kubilay Kocak <koobs at FreeBSD.org> ---
Hi Gert, thank you for your report. 

A reduced test case/program would be certainly by ideal, but also the following
information would be useful if you can provide it:

- Exact freebsd versions affected (uname -a)
- Minimum network configuration necessary to reproduce (/etc/rc.conf, openvpn
or pure tun/tap config (ideally))
- 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.

Additionally, we've had many changes in current since 12 was branched, I'd
probably test a 13-CURRENT snapshot too (the issue may have been identified and
resolved)

^Triage:  cc net/openvpn maintainer

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.