From: "Michał Pecio" <michal.pecio@gmail.com>
To: Lubomir Rintel <lkundrak@v3.sk>
Cc: linux-usb@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>
Subject: Re: [PATCH v3 net-next] rndis_host: Flag RNDIS modems as WWAN devices
Date: Sat, 12 Apr 2025 00:42:03 +0200 [thread overview]
Message-ID: <20250412004203.099e482a@foxbook> (raw)
In-Reply-To: <20250325095842.1567999-1-lkundrak@v3.sk>
On Tue, 25 Mar 2025 10:58:41 +0100, Lubomir Rintel wrote:
> Set FLAG_WWAN instead of FLAG_ETHERNET for RNDIS interfaces on Mobile
> Broadband Modems, as opposed to regular Ethernet adapters.
>
> Otherwise NetworkManager gets confused, misjudges the device type,
> and wouldn't know it should connect a modem to get the device to work.
> What would be the result depends on ModemManager version -- older
> ModemManager would end up disconnecting a device after an unsuccessful
> probe attempt (if it connected without needing to unlock a SIM), while
> a newer one might spawn a separate PPP connection over a tty interface
> instead, resulting in a general confusion and no end of chaos.
>
> The only way to get this work reliably is to fix the device type
> and have good enough version ModemManager (or equivalent).
>
> Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
> Fixes: 63ba395cd7a5 ("rndis_host: support Novatel Verizon USB730L")
Hi,
This patch appears to have caused a regression for some users,
who opened a bug against the USB subsystem here:
https://bugzilla.kernel.org/show_bug.cgi?id=220002
Regards,
Michal
next prev parent reply other threads:[~2025-04-11 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:58 [PATCH v3 net-next] rndis_host: Flag RNDIS modems as WWAN devices Lubomir Rintel
2025-03-25 11:13 ` Greg KH
2025-03-27 18:50 ` patchwork-bot+netdevbpf
2025-04-11 22:42 ` Michał Pecio [this message]
2025-04-12 5:08 ` Lars Melin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250412004203.099e482a@foxbook \
--to=michal.pecio@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.