Luci-proto-modemmanager support thread

I'm not sure why that is for you, for me the connection will start if

  1. I have a SIM in
  2. signal is available

You could put ModemManager into debug mode (see previous post) and post the logread output here if you want me to take a look. One thing you could do is script the ifup in your rc.local

Ok, I updated everything to the latest branch, set up the config file exactly as you suggested and this is the result after a normal boot (no connection is made):

https://pastebin.com/D49CQ3cD

Nothing happens, no matter how long I wait.

However, if I do stop and start the modem manager:

/etc/init.d# ./modemmanager stop
/etc/init.d# ./modemmanager start

after a few seconds the interface starts to work.

This is the log of the modemmanager stop/start event:

https://pastebin.com/QSqqZJAq

Can you please take a look what would the problem be?

Again, I might add that it maybe a driver issue, that too many maybe conflicting drivers are loaded? This is the relevant part of the kernel log:

[   16.722608] usbcore: registered new interface driver cdc_acm
[   16.726815] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[   16.801891] usbcore: registered new interface driver cdc_wdm
[   16.830163] Loading modules backported from Linux version v5.3-rc4-0-gd45331b00ddb
[   16.836323] Backport generated by backports.git v5.3-rc4-1-0-g4ec72687
[   16.897209] hso: drivers/net/usb/hso.c: Option Wireless
[   16.901354] usbcore: registered new interface driver hso
[   18.121968] usbcore: registered new interface driver usbserial
[   18.126459] usbcore: registered new interface driver usbserial_generic
[   18.133085] usbserial: USB Serial support registered for generic
[   18.483068] usbcore: registered new interface driver cdc_ether
[   18.641757] usbcore: registered new interface driver cdc_ncm
[   18.867019] usbcore: registered new interface driver huawei_cdc_ncm
[   19.527772] qmi_wwan 1-1.2:1.4: cdc-wdm0: USB WDM device
[   19.534489] qmi_wwan 1-1.2:1.4 wwan0: register 'qmi_wwan' at usb-ehci-platform-1.2, WWAN/QMI device, 2e:55:8c:d2:f1:c4
[   19.544169] usbcore: registered new interface driver qmi_wwan
[   19.555574] usbcore: registered new interface driver rndis_host
[   19.568581] usbcore: registered new interface driver sierra
[   19.572922] usbserial: USB Serial support registered for Sierra USB modem
[   19.588628] usbcore: registered new interface driver sierra_net
[   19.925907] usbcore: registered new interface driver cdc_mbim
[   19.942635] usbcore: registered new interface driver option
[   19.946864] usbserial: USB Serial support registered for GSM modem (1-port)
[   19.954698] option 1-1.2:1.0: GSM modem (1-port) converter detected
[   19.960382] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0
[   19.967479] option 1-1.2:1.1: GSM modem (1-port) converter detected
[   19.973625] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1
[   19.980701] option 1-1.2:1.2: GSM modem (1-port) converter detected
[   19.986720] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2
[   19.993903] option 1-1.2:1.3: GSM modem (1-port) converter detected
[   20.000010] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB3
[   20.098566] usbcore: registered new interface driver qcserial
[   20.103111] usbserial: USB Serial support registered for Qualcomm USB modem

Just a quick heads up, I will be able to test this with a Huawei 3372h-607 (150M down) USB 4G dongle soon. Will report back.

1 Like

Can you post the kernel log a bit later, where it says *your interface* becomes ready? One temporary workaround might be to add an ifup to your rc.local file

can someone tell me that how to install luci-proto-modemmanager via opkg

Should be:

okpg update
opkg install luci-proto-modemmanager

no it is not working

It's not part of the packages repository yet. nickberry17 is working to get this done, but its not quite there yet. the only way to get it today is to compile your own image and include it as a feed (and mung the Makefile because it's messed up, as of today at least).

Yes, and support for master (rather, anything beyond 18.06.x) is going to need a complete rewrite

can this protocol solve this error I am using QMI protocol at present

I have already done that but when I go in the network section on Luci there is no as such option for modemmanager.

ModemManager is now in master

1 Like

Boldly go...

Nice work getting this in and well done - yep, following the git trail there

sfx

is there a feature to send sms for this

No, but you can use mmcli directly

Do you not want to make sms support on luci-proto-modem manager? I see the GUI Webstools3 project is very good, I hope this is made and entered in the OpenWRT repo
(https://github.com/mahadirz/smstools3-openwrt-web)

Might be better to keep that separate as a luci-proto, as the context of where luci-proto-modemmanager is basically a one-shot to configure the interface.

MM is big enough as it is, it's high value to the community, but it does pull in a lot of code just outside of libqmi/libmbim - but the tradeoff there is worth it.

SMS on 3G/4G modems can be challenging - depending on what the modem supports - I've seen some that support SMS on the non-access stratum, others that do it over IP using IMS - and USSD (quick codes) can be a real challenge for some devices, even QMI based devices.

I think there is a lot of value to getting smstools into mainline, but it does take time to commit to being a package maintainer for it, and the effort to get it thru the peer review process to get it pulled in.

Eror

WARNING: Makefile 'package/feeds/luci/luci-app-cifsd/Makefile' has a dependency on 'cifsd-tools', which does not exist
WARNING: Makefile 'package/feeds/luci/luci-proto-modemmanager/Makefile' has a dependency on 'modemmanager', which does not exist
tmp/.config-package.in:104620:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
tmp/.config-package.in:104620:symbol PACKAGE_nfs-kernel-server depends on NFS_KERNEL_SERVER_V4
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
feeds/packages/net/nfs-kernel-server/Config.in:4:symbol NFS_KERNEL_SERVER_V4 depends on PACKAGE_nfs-kernel-server

I open an issue here as something is not right: https://github.com/openwrt/packages/issues/10565

this is working in 19.07.0-rc2.

1 Like