From: Kristof Provost Date: Tue, 30 Aug 2022 09:16:57 +0200 Message-ID: <51999814-F5D0-4D1C-BF91-7BEB3DAA2BDA@...2661...> In-Reply-To: <20220829190124.2636045-1-gert@...1296...> References: <20220829190124.2636045-1-gert@...1296...> MIME-Version: 1.0 Subject: Re: [Openvpn-devel] [PATCH] Adjust Linux+FreeBSD DCO device name handling to 'non DCO linux style' List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: Gert Doering Cc: openvpn-devel@lists.sourceforge.net On 29 Aug 2022, at 21:01, Gert Doering wrote: > On Linux, tun devices are created according to the following algorithm > --dev tun -> try tun0, tun1, ... tun255, use first free > --dev anything -> create a TUN device named "anything" > (as long as "anything" is not "null" or "tap[N]") > > DCO was following the "other platform convention", where everything > not having a digit was iterated ("--dev tun-home" -> "tun-home0") - > which does not work for classic tun/tap devices on the BSDs anyway, > so is not the best model. > > Adjust open_tun_dco_generic() to document expected behaviour and > do the thing. > > Signed-off-by: Gert Doering Acked-by: Kristof Provost Kristof