[OpenWrt-Devel] [ModemManager] How can I make ModemManager work right?

Jeonghum Joh oosaprogrammer at gmail.com
Mon May 11 02:28:02 EDT 2020


Hello Alexander and people,

I found one :
https://github.com/lkundrak/openwrt-network-manager

I wonder if this is righty and worthy to try.
I am now trying porting it anyway.

Thank you in advance.
Jeonghum

2020년 5월 11일 (월) 오후 2:56, Jeonghum Joh <oosaprogrammer at gmail.com>님이 작성:

> Hello Alexander and people who might concern,
>
> >>> In short, I'd like to know where I can find NetworkManager for
> openwrt. <<<
>
>
> I checked the vid:pid. It is "1519:0443". I found this via lsusb -v:
>
> SIERRA WIRELESS HL7528
> root at LEDE:~# lsusb -v
> Bus 001 Device 002: ID 1519:0443   <<<<<<<<<
> Bus 001 Device 001: ID 1d6b:0002
> Bus 002 Device 001: ID 1d6b:0003
>
> But I changed modem to new one because you said Sierra HL7528 would only
> work with ppp method and it's not supposed to be.
> Now I am testing with QUECTEL EC25-E MINIPCIE / EC25EFA MINIPCIE.
>
> It's vid:pid is shown:
>
> root at LEDE:~# lsusb -v
> Bus 001 Device 002: ID 2c7c:0125   <<<<<<<<<
> Bus 001 Device 001: ID 1d6b:0002
> Bus 002 Device 001: ID 1d6b:0003
>
> And now with this modem most prints look good:
>
> root at LEDE:~# mmcli -m 0
>   --------------------------------
>   General    |            dbus path: /org/freedesktop/ModemManager1/Modem/0
>                 |            device id:
> 97ffc2eeb6d3ad975d9089850aa3b9b494529919
>   --------------------------------
>   Hardware |         manufacturer: Quectel
>                |                model: EC25
>                |    firmware revision: EC25EFAR04A02M4G_SKT
>                |            supported: gsm-umts, lte
>                |              current: gsm-umts, lte
>                |         equipment id: 356673040475612
>   --------------------------------
>   System    |               device:
> /sys/devices/platform/1a0c0000.usb/usb1/1-2
>                 |              drivers: option
>                 |               plugin: Quectel
>                 |         primary port: ttyUSB2
>                 |                ports: ttyUSB0 (qcdm), ttyUSB2 (at),
> ttyUSB3 (at)
>   --------------------------------
>   Numbers  |                  own: 01224316205
>   --------------------------------
>   Status      |       unlock retries: sim-pin (3), sim-puk (10)
>                 |                state: enabled   <<<<<<<<<<<<<<<<<<<<<<<<
>                 |          power state: on
>                 |       signal quality: 0% (cached)
>   --------------------------------
>   Modes     |            supported: allowed: 2g, 3g, 4g; preferred: none
>                 |              current: allowed: 2g, 3g, 4g; preferred:
> none
>   --------------------------------
>   IP            |            supported: ipv4, ipv6, ipv4v6
>   --------------------------------
>   3GPP       |                 imei: 356673040475612
>                 |         registration: idle    <<<<<<<<<<<<<<<<<<<<<<<<
>   --------------------------------
>   3GPP EPS  | ue mode of operation: csps-1
>   --------------------------------
>   SIM         |            dbus path: /org/freedesktop/ModemManager1/SIM/0
>
> But some are not sure:
>
> root at LEDE:~# mmcli -b 0
> error: couldn't find bearer at '/org/freedesktop/ModemManager1/Bearer/0':
> 'not found in any modem'
>
> root at LEDE:~# mmcli -m 0 --list-bearers
> error: no actions specified
>
> I only enabled QMI via make menuconfig of openwrt.
> I didn't enable MBIM via make menuconfig of openwrt.
> I didn't look at the make kernel_menuconfig of openwrt.
>
> The state of Status is "enabled" and the registration of 3GPP is "idle".
> Does this mean the modem is connected to the bearer/operator network and
> the data usage is enabled?
>
> I found a documentation:
>
> https://docs.ubuntu.com/core/en/stacks/network/network-manager/docs/configure-cellular-connections
>
>
> This document shows using of "nmcli" to setup network interface like wwan.
> Do I need this also? I guess though.
> Do I need NetworkManager? If so, where can I get it? I searched from the
> place ( https://github.com/openwrt/packages.git ) where ModemManager for
> openwrt exist, but NetworkManager is not found there.
>
>
> And from the prints above, there are errors for "mmcli -b 0" and "mmcli -m
> 0 --list-bearers" I don't guess these errors are important but are they?
>
> F.Y.I. Let me show you entry for /etc/config/network
>
> config interface 'broadband'
>         option device '/sys/devices/platform/1a0c0000.usb/usb1/1-2'
>         option proto 'modemmanager'
>         option apn 'lte-internet.sktelecom.com'
>
> With this prints can I judge that the ModemManager is ported and working
> well?
>
> Thank you very much in advance.
> Jeonghum
>
> 2020년 5월 8일 (금) 오후 9:47, Aleksander Morgado <aleksander at aleksander.es>님이
> 작성:
>
>> Hey,
>>
>> > We have Sierra modem. HL7528
>> > So I tested my linux box with this modem and I received first prints
>> below:
>> >
>> > root at LEDE:/lib/udev/rules.d# mmcli -L
>> >     /org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless] HL7528
>> > root at LEDE:/lib/udev/rules.d# mmcli -m 0
>> >   -----------------------------
>> >   General  |         dbus path: /org/freedesktop/ModemManager1/Modem/0
>> >            |         device id: a643b0bb58dac30a2cd4ff6b486e826b483d298b
>> >   -----------------------------
>> >   Hardware |      manufacturer: Sierra Wireless
>> >            |             model: HL7528
>> >            | firmware revision:
>> THL7528_778_tb3_utp426.0.0.152000.202004221951.x7160_1
>> >            |         supported: gsm-umts, lte
>> >            |           current: gsm-umts, lte
>> >            |      equipment id: 356170062941712
>> >   -----------------------------
>> >   System   |            device:
>> /sys/devices/platform/1a0c0000.usb/usb1/1-2
>> >            |           drivers: cdc_acm, cdc_ncm
>> >            |            plugin: Generic
>> >            |      primary port: ttyACM0
>> >            |             ports: wwan3 (net), ttyACM0 (at), wwan0 (net),
>> wwan1 (net),
>> >            |                    wwan2 (net), ttyACM2 (at)
>> >   -----------------------------
>> >   Status   |             state: failed
>> >            |     failed reason: sim-missing
>> >            |       power state: on
>> >            |    signal quality: 0% (cached)
>> >   -----------------------------
>> >   Modes    |         supported: allowed: 2g, 3g, 4g; preferred: none
>> >            |           current: allowed: any; preferred: none
>> >
>> > I did this test to verify if my applying ModemManager have any issue.
>> With this print result, can I judge that ModemManager is ported well?
>> >
>>
>> Is this device relatively new? What is the "vid:pid" of the device?
>> Could you get a full "lsusb -v" output of the device?
>>
>> I see the modem is exposing multiple AT and net ports, but
>> unfortunately ModemManager doesn't know how to handle those net ports,
>> so if you get that modem connected it will be using PPP over a TTY,
>> which is not optimal. The connection and management will work, but it
>> won't be as good as it can be,
>>
>> > I from now on will test with this modem. I think I need rule file for
>> this modem and I found one:
>> > /lib/udev/rules.d/77-mm-sierra.rules
>> >
>> > The content of this rule file:
>> >
>> > # do not edit this file, it will be overwritten on update
>> > ACTION!="add|change|move|bind", GOTO="mm_sierra_end"
>> > SUBSYSTEMS=="usb", ATTRS{idVendor}=="1199", GOTO="mm_sierra"
>> > GOTO="mm_sierra_end"
>> >
>> > LABEL="mm_sierra"
>> > SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*",
>> ENV{.MM_USBIFNUM}="$attr{bInterfaceNumber}"
>> >
>> > # Netgear AC341U: enable connection status polling explicitly
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9057",
>> ENV{ID_MM_QMI_CONNECTION_STATUS_POLLING_ENABLE}="1"
>> >
>> > # MC74XX: Add port hints
>> > #  if 03: primary port
>> > #  if 02: raw NMEA port
>> > #  if 00: diag/qcdm port
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
>> ENV{.MM_USBIFNUM}=="03", ENV{ID_MM_PORT_TYPE_AT_PRIMARY}="1"
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
>> ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_PORT_TYPE_GPS}="1"
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9071",
>> ENV{.MM_USBIFNUM}=="00", ENV{ID_MM_PORT_TYPE_QCDM}="1"
>> >
>> > # EM7565: Add port hints
>> > #  if 03: primary port
>> > #  if 02: raw NMEA port
>> > #  if 00: diag/qcdm port
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9091",
>> ENV{.MM_USBIFNUM}=="03", ENV{ID_MM_PORT_TYPE_AT_PRIMARY}="1"
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9091",
>> ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_PORT_TYPE_GPS}="1"
>> > ATTRS{idVendor}=="1199", ATTRS{idProduct}=="9091",
>> ENV{.MM_USBIFNUM}=="00", ENV{ID_MM_PORT_TYPE_QCDM}="1"
>> >
>> > LABEL="mm_sierra_end"
>> >
>> >
>> > Is this rule file fit to my modem?
>> > Or do I need new rule file for this modem?
>> >
>>
>> The rule files are "helpers" really, there is no need for the rule
>> files usually. In your case, I believe the modem isn't using any of
>> the rule files that ModemManager provides.
>>
>> > And do I need special settings in /etc/config/network ? I know basic
>> settings for this:
>> > config interface 'broadband'
>> >         option device '/sys/devices/platform/1a0c0000.usb/usb1/1-2'
>> >         option proto 'modemmanager'
>> >         option apn 'whatever corect apn here'
>> >         option username ''
>> >         option password ''
>> >         option pincode ''
>> >         option lowpower '1'
>> >
>>
>> As in the previous email, you probably don't need username, password,
>> and lowpower. And you only need pincode if your SIM card is
>> PIN-locked, which may not be.
>>
>> Cheers!
>>
>> --
>> Aleksander
>> https://aleksander.es
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20200511/4525c693/attachment.htm>
-------------- next part --------------
_______________________________________________
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel


More information about the openwrt-devel mailing list