packages/net/modemmanager
Florian Eckert 0b027b131c ModemManager: refactoring procd init script
The way the init script is written now, we get a bad output when calling
the ubus service backend.

ubus call service list "{'verbose':true,'name':'modemmanager'}"
>{
>        "modemmanager": {
>                "instances": {
>                        "instance1": {
>                                "running": true,
>                                "pid": 20511,
>                                "command": [
>                                        "sh",
>                                        "-c",
>                                        ".
>/usr/share/ModemManager/modemmanager.common;    \t
>mkdir -m 0755 -p /var/run/modemmanager;          \t
>mm_cleanup_interfaces;                            \t
>( mm_report_events_from_cache ) >/dev/null 2>&1 & \t
>/usr/sbin/ModemManager"
>                                ],
>                                "term_timeout": 5,
>                                "respawn": {
>                                        "threshold": 3600,
>                                        "timeout": 5,
>                                        "retry": 5
>                                },
>                                "pidfile":"/var/run/modemmanager/modemmanager.pid"
>                        }
>                }
>        }
>}"

I also get the output in the log that the PID file cannot be created.

> daemon.err procd: Failed to remove pidfile: :No such file or directory

The changes in this commit fixes this issues, by moving startup into a
wrapper script.

Signed-off-by: Florian Eckert <fe@dev.tdt.de>
2021-12-06 14:49:43 +01:00
..
files ModemManager: refactoring procd init script 2021-12-06 14:49:43 +01:00
Config.in modemmanager: added new proto options 2020-08-13 12:56:31 +03:00
Makefile ModemManager: refactoring procd init script 2021-12-06 14:49:43 +01:00
README.md modemmanager: added new proto options 2020-08-13 12:56:31 +03:00

OpenWrt ModemManager

Description

Cellular modem control and connectivity

Optional libraries libmbim and libqmi are available. Your modem may require additional kernel modules and/or the usb-modeswitch package.

Usage

Once installed, you can configure the 2G/3G/4G modem connections directly in /etc/config/network as in the following example:

config interface 'broadband'
    option device      '/sys/devices/platform/soc/20980000.usb/usb1/1-1/1-1.2/1-1.2.1'
    option proto       'modemmanager'
    option apn         'ac.vodafone.es'
    option allowedauth 'pap chap'
    option username    'vodafone'
    option password    'vodafone'
    option pincode     '7423'
    option iptype      'ipv4'
    option lowpower    '1'
    option signalrate  '30'

Only 'device' and 'proto' are mandatory options, the remaining ones are all optional.

The 'allowedauth' option allows limiting the list of authentication protocols. It is given as a space-separated list of values, including any of the following: 'pap', 'chap', 'mschap', 'mschapv2' or 'eap'. It will default to allowing all protocols.

The 'iptype' option supports any of these values: 'ipv4', 'ipv6' or 'ipv4v6'. It will default to 'ipv4' if not given.

The 'signalrate' option set's the signal refresh rate (in seconds) for the device. You can call signal info with command: mmcli -m 0 --signal-get