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 Dominik Nille Technology Innovation Management [http://assets.balluff.com/JPG_original_size/E-Mail-Footer_Vertrieb_Logo.jpg] Balluff GmbH * Schurwaldstrasse 9 * 73765 Neuhausen a.d.F. * Germany Phone +497158173-8020 * Fax +4971585010 * dominik.ni...@balluff.de<mailto:dominik.ni...@balluff.de> * www.balluff.com<http://www.balluff.com> [Facebook]<https://de-de.facebook.com/balluff.gmbh> [LinkedIn] <https://www.linkedin.com/company/balluff-gmbh-germany> [Twitter] <https://twitter.com/balluff?lang=de> [Youtube] <https://www.youtube.com/user/BalluffSensors> [Xing] <https://www.xing.com/companies/balluffgmbh> [Blog] <https://www.innovating-automation.blog/?lang=de> 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 [http://assets.balluff.com/JPG_original_size/E-Mail-Footer_Vertrieb_Claim.jpg]
