<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> RESEND On 21/10/2020 3:59 pm, Brendan Simon (eTRIX) wrote: <blockquote type="cite" cite="mid:fb6ed353-d116-f3d7-37da-c075d6a13e0f@etrix.com.au"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> On 19/08/2020 2:13 am, Aleksander Morgado wrote: <blockquote type="cite" cite="mid:CAAP7uc+w9uL1hZKLXQ9Jn8C0BpRC0GeQzp2W6FnUakdcwmqMyw@mail.gmail.com"> <blockquote type="cite"> <pre class="moz-quote-pre" wrap="">There is a recent patch to avoid this, by avoiding the use of "NAS Register in Network" and use "NAS Set System Selection Preference" instead: <a class="moz-txt-link-freetext" href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/c70b3557184fdf1472ff0cb36e9fd937cc7f9024" moz-do-not-send="true">https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/c70b3557184fdf1472ff0cb36e9fd937cc7f9024</a> </pre> </blockquote> </blockquote> So it's been a while, but I now have MM 1.14.2 installed on my embedded system via Debian Buster Backports repo. I can successfully set the allowed mode to "3G" and get a UMTS connection. mmcli -m 0 --set-allowed-modes="3G" However, if I try to lock to 4G the connection never succeeds. mmcli -m 0 --set-allowed-modes="4G" The only way I can get an LTE connection is with the following. mmcli -m 0 --set-allowed-modes="3G|4G" --set-preferred-mode=4G Is this a bug? Maybe there is something else going on? Any ideas or suggestions to get an LTE connection with setting 4G as the only allowed mode? </blockquote> </body> </html>