<div dir="ltr">Hello Bjørn,<div><br></div><div>Thank you for the very kind message!</div><div>I tried "mmcli -L" and received an error message:</div><div> root at LEDE:~# mmcli -L<br></div><div> error: couldn't create manager: Timeout was reached</div><div><br></div><div>I added "--debug" option into the ModemManager start command.</div><div>I used device path: "/sys/devices/platform/1a0c0000.usb/usb2/2-1" in the /etc/config/network.</div><div><br></div><div>And I got an logread output file.</div><div>I will attach it to this email.</div><div><br></div><div>I already posted this question to the ModemManager maillist also:</div><div><a href="https://lists.freedesktop.org/archives/modemmanager-devel/2020-May/007798.html">https://lists.freedesktop.org/archives/modemmanager-devel/2020-May/007798.html</a> </div><div><br></div><div>So now I'm waiting Alexander's reply message about my problem.</div><div>But, If you have any idea, please let me know.</div><div><br></div><div>And the verison of OpenWRT I use, I will try to change it to the later version later, if I am allowd. I have not that much right to decide in this company.</div><div><br></div><div>Thank you very much in advance!</div><div><br></div><div>Jeonghum</div><div> <br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2020년 4월 29일 (수) 오후 7:56, Bjørn Mork <<a href="mailto:bjorn@mork.no">bjorn@mork.no</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Michael Jones <<a href="mailto:mike@meshplusplus.com" target="_blank">mike@meshplusplus.com</a>> writes:<br>
<br>
> Instead, before using netifd, try talking directly to modemmanager using<br>
> "mmcli".<br>
<br>
Agreed. Verify that MM has detected the modem, and haven't found<br>
anything wrong with it. That's the first step.<br>
<br>
Run<br>
<br>
mmcli -L<br>
<br>
to list all modems, and<br>
<br>
mmcli -m X<br>
<br>
to look at the details for one of them where X is the number of the<br>
modem. An example:<br>
<br>
root@wrt1900ac-1:~# mmcli -L<br>
/org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] EM7565<br>
root@wrt1900ac-1:~# mmcli -m 0<br>
--------------------------------<br>
General | dbus path: /org/freedesktop/ModemManager1/Modem/0<br>
| device id: af4c825714288908db4d5d2cca50e0d26cdc8bb5<br>
--------------------------------<br>
Hardware | manufacturer: Sierra Wireless, Incorporated<br>
| model: EM7565<br>
| firmware revision: SWI9X50C_01.11.00.00 5ba42f jenkins 2019/06/28 09:51:52<br>
| carrier config: default<br>
| h/w revision: 0.6<br>
| supported: gsm-umts, lte<br>
| current: gsm-umts, lte<br>
| equipment id: 359260080xxxxxx<br>
--------------------------------<br>
System | device: /sys/devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:01.0/0000:01:00.0/usb3/3-2<br>
| drivers: qmi_wwan, qcserial<br>
| plugin: Sierra<br>
| primary port: cdc-wdm0<br>
| ports: cdc-wdm0 (qmi), ttyUSB4 (qcdm), ttyUSB5 (gps), <br>
| ttyUSB6 (at), wwan0 (net)<br>
--------------------------------<br>
Status | lock: sim-pin2<br>
| unlock retries: sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 (10)<br>
| state: connected<br>
| power state: on<br>
| access tech: lte<br>
| signal quality: 84% (recent)<br>
--------------------------------<br>
Modes | supported: allowed: 3g; preferred: none<br>
| allowed: 4g; preferred: none<br>
| allowed: 3g, 4g; preferred: 3g<br>
| allowed: 3g, 4g; preferred: 4g<br>
| current: allowed: 3g, 4g; preferred: 4g<br>
--------------------------------<br>
Bands | supported: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8, <br>
| utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, <br>
| eutran-7, eutran-8, eutran-9, eutran-12, eutran-13, eutran-18, <br>
| eutran-19, eutran-20, eutran-26, eutran-28, eutran-29, eutran-30, <br>
| eutran-32, eutran-41, eutran-42, eutran-43, eutran-46, eutran-48, <br>
| eutran-66, utran-19<br>
| current: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8, <br>
| utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, <br>
| eutran-7, eutran-8, eutran-9, eutran-12, eutran-13, eutran-18, <br>
| eutran-19, eutran-20, eutran-26, eutran-28, eutran-29, eutran-30, <br>
| eutran-32, eutran-41, eutran-42, eutran-43, eutran-46, eutran-48, <br>
| eutran-66, utran-19<br>
--------------------------------<br>
IP | supported: ipv4, ipv6, ipv4v6<br>
--------------------------------<br>
3GPP | imei: 359260080xxxxxx<br>
| operator id: 24201<br>
| operator name: TELENOR<br>
| registration: home<br>
--------------------------------<br>
3GPP EPS | ue mode of operation: csps-2<br>
--------------------------------<br>
SIM | dbus path: /org/freedesktop/ModemManager1/SIM/0<br>
--------------------------------<br>
Bearer | dbus path: /org/freedesktop/ModemManager1/Bearer/0<br>
<br>
<br>
<br>
<br>
This will verify that<br>
- the device path is correct and was found,<br>
- the proper kernel devices were found by MM and probed OK,<br>
- the SIM is connected and unlocked, and<br>
- that the modem has registered in the network<br>
<br>
It might not show connected, like mine does, but that's the next step. <br>
<br>
When everything looks OK, you can try to connect with<br>
<br>
ifup XXX<br>
<br>
where XXX is your modem interface name from the config. Use<br>
<br>
ifstatus XXX<br>
<br>
look at the IP configuration when connected. For example, my interface<br>
entry is named 'mm' (note that the "ip4table" is a special thing for my<br>
environment - no need to copy this):<br>
<br>
config interface 'mm'<br>
option device '/sys/devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:01.0/0000:01:00.0/usb3/3-2'<br>
option proto 'modemmanager'<br>
option apn 'internet.public'<br>
option pincode 'xxxx'<br>
option iptype 'ipv4'<br>
option ip4table '42'<br>
<br>
<br>
so the IP session can be inspected by:<br>
<br>
<br>
root@wrt1900ac-1:~# ifstatus mm<br>
{<br>
"up": true,<br>
"pending": false,<br>
"available": true,<br>
"autostart": true,<br>
"dynamic": false,<br>
"uptime": 335711,<br>
"l3_device": "wwan0",<br>
"proto": "modemmanager",<br>
"updated": [<br>
"addresses",<br>
"routes"<br>
],<br>
"ip4table": 42,<br>
"metric": 0,<br>
"dns_metric": 0,<br>
"delegation": true,<br>
"ipv4-address": [<br>
{<br>
"address": "77.18.146.13",<br>
"mask": 30<br>
}<br>
],<br>
"ipv6-address": [<br>
<br>
],<br>
"ipv6-prefix": [<br>
<br>
],<br>
"ipv6-prefix-assignment": [<br>
<br>
],<br>
"route": [<br>
{<br>
"target": "0.0.0.0",<br>
"mask": 0,<br>
"nexthop": "77.18.146.14",<br>
"source": "<a href="http://77.18.146.13/32" rel="noreferrer" target="_blank">77.18.146.13/32</a>"<br>
}<br>
],<br>
"dns-server": [<br>
"193.213.112.4",<br>
"130.67.15.198"<br>
],<br>
"dns-search": [<br>
<br>
],<br>
"neighbors": [<br>
<br>
],<br>
"inactive": {<br>
"ipv4-address": [<br>
<br>
],<br>
"ipv6-address": [<br>
<br>
],<br>
"route": [<br>
<br>
],<br>
"dns-server": [<br>
<br>
],<br>
"dns-search": [<br>
<br>
],<br>
"neighbors": [<br>
<br>
]<br>
},<br>
"data": {<br>
<br>
}<br>
}<br>
<br>
<br>
<br>
<br>
An overlapping set of this is also available with mmcli, using the<br>
bearer reference you'll find in the overview when connected:<br>
<br>
<br>
root@wrt1900ac-1:~# mmcli -b 0<br>
--------------------------------<br>
General | dbus path: /org/freedesktop/ModemManager1/Bearer/0<br>
| type: default<br>
--------------------------------<br>
Status | connected: yes<br>
| suspended: no<br>
| interface: wwan0<br>
| ip timeout: 20<br>
--------------------------------<br>
Properties | apn: internet.public<br>
| roaming: allowed<br>
| ip type: ipv4<br>
--------------------------------<br>
IPv4 configuration | method: static<br>
| address: 77.18.146.13<br>
| prefix: 30<br>
| gateway: 77.18.146.14<br>
| dns: 193.213.112.4, 130.67.15.198<br>
| mtu: 1500<br>
--------------------------------<br>
Statistics | duration: 336240<br>
| bytes rx: 676026<br>
| bytes tx: 562276<br>
<br>
<br>
<br>
<br>
Hope that's enough to get you started.<br>
<br>
And I totally agree: Upgrade to a recent OpenWrt. Doing development on<br>
an arbitrary 17.01 snapshot is pointless.<br>
<br>
<br>
<br>
Bjørn<br>
</blockquote></div>