Jason A. Donenfeld 4cd06c0925 tun: openbsd: check for interface already being up ... In some cases, we operate on an already-up interface, or the user brings up the interface before we start monitoring. For those situations, we should first check if the interface is already up. This still technically races between the initial check and the start of the route loop, but fixing that is a bit ugly and probably not worth it at the moment. Reported-by: Theo Buehler <tb@theobuehler.org>		2019-09-07 00:13:23 -05:00
..
wintun	namespaceapi: AddSIDToBoundaryDescriptor modifies the handle	2019-09-05 21:48:21 -06:00
operateonfd.go	receive: implement flush semantics	2019-03-21 14:45:41 -06:00
tun.go	tun: remove TUN prefix from types to reduce stutter elsewhere	2019-06-14 18:35:57 +02:00
tun_darwin.go	tun: darwin: do not attempt to close tun.event twice	2019-08-02 12:24:17 +02:00
tun_freebsd.go	tun: remove TUN prefix from types to reduce stutter elsewhere	2019-06-14 18:35:57 +02:00
tun_linux.go	tun: remove TUN prefix from types to reduce stutter elsewhere	2019-06-14 18:35:57 +02:00
tun_openbsd.go	tun: openbsd: check for interface already being up	2019-09-07 00:13:23 -05:00
tun_windows.go	wintun: take mutex so that deletion uses the right name	2019-08-30 15:34:17 +02:00