<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'> Hi Dominik, Your issues might be related to the introduction of QMI PCO in ModemManager 1.20 commit <a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/af9b6d4f2d7e43e2092d16afdae7ad38f7f55163">af9b6d4f</a>. If no valid PCO information is returned, you'll get the mm_utils_bin2hexstr assertion error, which was later fixed in ModemManager 1.20.6, see <a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/740#note_1963193">#740 (comment 1963193)</a>. So running a newer version of ModemManager might improve your situation. You might also try the older ModemManager 1.18 that does not include QMI PCO. I'm struggling myself with a similar PCO issue where simply requesting the new QMI_WDS_REQUESTED_SETTINGS_OPERATOR_RESERVED_PCO setting crashes the modem, see <a href="https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/842#note_2521001">#842 comment 2521001</a>. To me, it seems like older modems dislike PCO and extended IP configuration Indication. null On 2024-08-16 14:02, Dominik Nille wrote: <blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"> <style type="text/css">@font-face { font-family: "Cambria Math"; } @font-face { font-family: Calibri; } @font-face { font-family: "Roboto Flex Normal"; } #replybody1 p.MsoNormal, #replybody1 li.MsoNormal, #replybody1 div.MsoNormal { margin: 0cm; font-size: 11.0pt; font-family: "Roboto Flex Normal"; mso-ligatures: standardcontextual; mso-fareast-language: EN-US; } #replybody1 span.E-MailFormatvorlage46 { mso-style-type: personal-compose; font-family: "Roboto Flex Normal"; color: windowtext; } #replybody1 .MsoChpDefault { mso-style-type: export-only; font-size: 10.0pt; font-family: "Roboto Flex Normal"; mso-ligatures: standardcontextual; mso-fareast-language: EN-US; } @page WordSection1 { size: 612.0pt 792.0pt; margin: 70.85pt 70.85pt 2.0cm 70.85pt; } #replybody1 div.WordSection1 {}</style> <div id="replybody1" lang="DE" style="word-wrap: break-word;"> <div class="v1WordSection1"> Hi, I use a “Quectel Wireless Solutions Co., Ltd. RM520N-GL“ to connect to cellular neworks (in this example 1nce) After setting the initialbearer mmcli -m any --3gpp-set-initial-eps-bearer-settings="apn=iot.1nce.net,ip-type=ipv4v6" Modifying the nmcli connection nmcli c mod wwan gsm.apn iot.1nce.net autoconnect yes and trying to bring up the connection. nmcli c up wwan The modem takes a really long time to connect to the network. It seems that the nmcli does wait for the modem state to be connected. I did grep the journal of mmcli to check what is taking that long and I got some warnings in simple connect state (6/10): register. Aug 16 08:26:09 ModemManager[456]: <info> [modem0] 3GPP registration state changed (roaming -> registering) Aug 16 08:26:09 ModemManager[456]: <info> [modem0] 3GPP registration state changed (registering -> roaming) Aug 16 08:26:10 ModemManager[456]: <info> [modem0] 3GPP registration state changed (roaming -> unknown) Aug 16 08:26:10 ModemManager[456]: <info> [modem0] state changed (registered -> enabled) Aug 16 08:26:19 ModemManager[456]: <info> [modem0] simple connect started... Aug 16 08:26:19 ModemManager[456]: <info> [modem0] simple connect state (6/10): register Aug 16 08:26:26 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:26:36 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:26:47 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:26:56 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:27:06 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:27:17 ModemManager[456]: <warn> [modem0] couldn't reload extended signal information: No way to load extended signal information Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] network reject indication received Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] service domain: ps Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] radio interface: 5gnr Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] reject cause: (null) Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] mcc: 262 Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] mnc: 1 Aug 16 08:27:19 ModemManager[456]: <warn> [modem0] closed subscriber group: 27 Aug 16 08:27:19 ModemManager[456]: <info> [modem0] 3GPP registration state changed (unknown -> idle) Aug 16 08:27:19 ModemManager[456]: <info> [modem0] simple connect started... Aug 16 08:27:19 ModemManager[456]: <info> [modem0] simple connect state (6/10): register Aug 16 08:27:20 ModemManager[456]: <info> [modem0] 3GPP registration state changed (idle -> unknown) Aug 16 08:27:21 ModemManager[456]: <info> [modem0] 3GPP registration state changed (unknown -> registering) Aug 16 08:27:21 ModemManager[456]: <info> [modem0] 3GPP registration state changed (registering -> roaming) Aug 16 08:27:21 ModemManager[456]: <info> [modem0] state changed (enabled -> registered) Aug 16 08:27:22 ModemManager[456]: <info> [modem0] 3GPP registration state changed (roaming -> registering) Aug 16 08:27:22 ModemManager[456]: <info> [modem0] 3GPP registration state changed (registering -> roaming) Aug 16 08:27:22 ModemManager[456]: <info> [modem0] simple connect state (7/10): wait to get packet service state attached Aug 16 08:27:22 ModemManager[456]: <info> [modem0] simple connect state (8/10): bearer Aug 16 08:27:22 ModemManager[456]: <info> [modem0] simple connect state (9/10): connect Aug 16 08:27:22 ModemManager[456]: <info> [modem0] state changed (registered -> connecting) Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] QMI IPv4 Settings: Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] address: 100.76.105.26/30 Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] gateway: 100.76.105.25 Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] DNS #1: 8.8.8.8 Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] DNS #2: 8.8.4.4 Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] MTU: 1500 Aug 16 08:27:23 ModemManager[456]: <error> mm_utils_bin2hexstr: assertion 'bin != NULL' failed Aug 16 08:27:23 ModemManager[456]: <info> [modem0/bearer3] reloading stats is supported by the device Aug 16 08:27:23 ModemManager[456]: <info> [modem0] state changed (connecting -> connected) Aug 16 08:27:23 ModemManager[456]: <info> [modem0] simple connect state (10/10): all done It seems like the connection process takes a long time during the errors “couldn't reload extended signal information: No way to load extended signal information”. Any idea or recommendation, how I can fix it? Best regards, Dominik </div> <div>Dominik Nille</div> Technology Innovation Management <img src="cid:172413798066c441fc3e03d945099754@disroot.org" align="bottom" border="0" hspace="0" /> Balluff GmbH · Schurwaldstrasse 9 · 73765 Neuhausen a.d.F. · Germany Phone +497158173-8020 · Fax +4971585010 · <a style="color: black;" href="mailto:Dominik.Nille@balluff.de" rel="noreferrer"> Dominik.Nille@balluff.de</a> · <a style="color: black;" href="http://www.balluff.com" target="_blank" rel="noopener noreferrer"> www.balluff.com</a> <a style="color: black;" href="https://de-de.facebook.com/balluff.gmbh" target="_blank" rel="noopener noreferrer"><img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="Facebook" height="26" border="0" /></a> <a style="color: black;" href="https://www.linkedin.com/company/balluff-gmbh-germany" target="_blank" rel="noopener noreferrer"> <img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="LinkedIn" height="26" border="0" /></a> <a style="color: black;" href="https://twitter.com/balluff?lang=de" target="_blank" rel="noopener noreferrer"> <img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="Twitter" height="26" border="0" /></a> <a style="color: black;" href="https://www.youtube.com/user/BalluffSensors" target="_blank" rel="noopener noreferrer"> <img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="Youtube" height="26" border="0" /></a> <a style="color: black;" href="https://www.xing.com/companies/balluffgmbh" target="_blank" rel="noopener noreferrer"> <img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="Xing" height="26" border="0" /></a> <a style="color: black;" href="https://www.innovating-automation.blog/?lang=de" target="_blank" rel="noopener noreferrer"> <img src="cid:172413798066c441fc3e03d945099754@disroot.org" alt="Blog" height="26" border="0" /></a> Place of incorporation/Sitz der Gesellschaft: Neuhausen a.d.F., Germany · Register court/Registergericht: Amtsgericht Stuttgart, Germany Trade register/Handelsregister: HRB 214038 · Managing directors/Geschäftsführer: Katrin Stegmaier-Hermle, Florian Hermle, Frank Nonnenmann Chairman board of directors/Vorsitzender des Aufsichtsrats: Michael Unger · VAT ID/USt-ID: DE213 402 337 <img src="cid:172413798066c441fc3e03d945099754@disroot.org" align="bottom" border="0" hspace="0" /> </div> </blockquote> </body></html>