[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 Kubilay Kocak changed: What|Removed |Added Flags||maintainer-feedback?(bz@Fre ||eBSD.org) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #8 from Gert Doering --- I do not understand enough of the FreeBSD IPv6 magic bits to reasonably argue either way. The rc.conf of this system is very minimal -- cut hostname="fbsd-tc.ov.greenie.net" ifconfig_em0="inet 194.97.140.21 netmask 255.255.255.224" defaultrouter="194.97.140.30" ipv6_defaultrouter="2001:608:0:814::" ifconfig_em0_ipv6="inet6 2001:608:0:814::f000:21/64" sshd_enable="YES" ntpdate_enable="YES" ntpd_enable="YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev="AUTO" zfs_enable="YES" inetd_enable=YES# gert, 30.9.19, amanda -- cut but I'd still argue it should be deterministic either way, like "always IFFIDSABLED" or "never". Anyway, test program coming. Might take until tomorrow. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #7 from Kyle Evans --- (In reply to Kyle Evans from comment #6) s/nd6/ndp/ -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 Kyle Evans changed: What|Removed |Added CC||b...@freebsd.org --- Comment #6 from Kyle Evans --- (In reply to Gert Doering from comment #5) Interesting; if you're not getting at least this message: $ifname: possible hardware address duplication detected, disable IPv4 Then, AFAICT, this probably indicates that rtsold or nd6 has for some reason explicitly disabled it... I guess probably the former. CC'ing bz@ because I'm less sure now that it's specifically a tun/tap issue and not a broader issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #5 from Gert Doering --- (In reply to Kyle Evans from comment #3) nd6_dad_timer: cancel DAD on tun0 because of ND6_IFF_IFDISABLED. nd6_dad_timer: cancel DAD on tun0 because of ND6_IFF_IFDISABLED. this is what I have, but it's sort of not explaining "why ifdisabled" but just logging the consequences. Might this be related? nd6_dad_timer: called with non-tentative address fe80:3::250:56ff:fe9c:dffb(tun0) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #4 from Gert Doering --- 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. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #3 from Kyle Evans --- Is there any additional information about the interface in the syslog? It looks like there's only three possible places that ND6_IFF_IFDISABLED can be set, and two of them output errors: $ifname: possible hardware address duplication detected, disable IPv4 Cannot enable an interface with a link-local address marked duplicate. Noting that the second message doesn't indicate an interface name. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 Kyle Evans changed: What|Removed |Added Assignee|n...@freebsd.org |kev...@freebsd.org CC||kev...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 Kubilay Kocak changed: What|Removed |Added Status|New |Open Keywords||needs-qa, regression Severity|Affects Only Me |Affects Some People Flags||mfc-stable12? Assignee|b...@freebsd.org|n...@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||mand...@freebsd.org, ||n...@freebsd.org --- Comment #1 from Kubilay Kocak --- 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. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
[Bug 248172] tun/tap: OpenVPN configuring tun/tap devices ends up with IFDISABLED interfaces
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248172 --- Comment #2 from Kyle Evans --- (In reply to Gert Doering from comment #0) Hi, If you could provide me a test case that reproduces it somewhat reliably, I'd appreciate it; in 12.2, tun/tap have been consolidated into a single driver and some other races fixed along the way. You could try testing on recent stable/12 to see if you can reproduce it at all before reduced test case. I'll look over the driver briefly and see if I can spot an immediate issue along these lines. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
