From owner-freebsd-usb@freebsd.org Tue Sep 1 13:54:54 2020 Return-Path: Delivered-To: freebsd-usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4327C3C8C73 for ; Tue, 1 Sep 2020 13:54:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4BgpV60TFvz4YFt for ; Tue, 1 Sep 2020 13:54:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: by mailman.nyi.freebsd.org (Postfix) id 103943C8F26; Tue, 1 Sep 2020 13:54:54 +0000 (UTC) Delivered-To: usb@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 100113C8CAF for ; Tue, 1 Sep 2020 13:54:54 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router10G.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BgpV52CvRz4Y4g for ; Tue, 1 Sep 2020 13:54:52 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router10g.digiware.nl (localhost.digiware.nl [127.0.0.1]) by router10G.digiware.nl (Postfix) with ESMTP id 7DBB769A31; Tue, 1 Sep 2020 15:54:50 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from router10G.digiware.nl ([127.0.0.1]) by router10g.digiware.nl (router10g.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lwiEVfdYMLkT; Tue, 1 Sep 2020 15:54:49 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by router10G.digiware.nl (Postfix) with ESMTPSA id CB00B69A30; Tue, 1 Sep 2020 15:54:49 +0200 (CEST) Subject: Re: USB-dongle modem keeps changing from cuaU0 to cuaU1 and bck To: Hans Petter Selasky , usb@freebsd.org References: From: Willem Jan Withagen Message-ID: <8ffb4077-b0cb-ed0c-bd86-9fa164ae140d@digiware.nl> Date: Tue, 1 Sep 2020 15:54:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: nl X-Rspamd-Queue-Id: 4BgpV52CvRz4Y4g X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wjw@digiware.nl designates 2001:4cb8:90:ffff::3 as permitted sender) smtp.mailfrom=wjw@digiware.nl X-Spamd-Result: default: False [-1.64 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.04)[-1.040]; MIME_GOOD(-0.10)[text/plain]; HFILTER_HELO_IP_A(1.00)[router10g.digiware.nl]; HFILTER_HELO_NORES_A_OR_MX(0.30)[router10g.digiware.nl]; DMARC_NA(0.00)[digiware.nl]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.59)[-0.592]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.01)[-1.010]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:28878, ipnet:2001:4cb8::/29, country:NL]; RCVD_TLS_LAST(0.00)[]; MAILMAN_DEST(0.00)[usb] X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2020 13:54:54 -0000 On 1-9-2020 15:37, Hans Petter Selasky wrote: > On 2020-09-01 15:34, Willem Jan Withagen wrote: >> Is there any particular reason for the OS to assign a different port? > > If the device is always present during boot, then numbers are fixed. It is, it is in a offsite rackserver where we run Nagios monitoring. Dongle is never removed. Server was not rebooted, but still between yesterday noon en today noon it changed ports. Could it be because the dongle itself crashes? > >> And can I prevent that from changing? > > You can create a devd rule which matches the creation of /dev/cuaUX, > and then there is some more information which allows you to decide > which device is which. > > See also discussion at: > > https://reviews.freebsd.org/D21886 Will check. --WjW