MODEMMANAGER(8)

๐Ÿ“ฆ
version 1.25.95_git20260527 ยท 2 versions
  • 1.25.95_git20260527 ยท alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.18.6 ยท ubuntu jammy
, in alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

๐Ÿ’– MODEMMANAGER(8) ๐Ÿ’–

โœจ NAME โœจ

okay so the name of this thing is ModemManager, and it's a mobile broadband modem management daemon ๐Ÿ“ฑ๐Ÿฆ‹

๐ŸŽ€ SYNOPSIS ๐ŸŽ€

ModemManager [OPTION...]

๐Ÿ’… DESCRIPTION ๐Ÿ’…

okay so ModemManager gives you one unified, high level API for talking to mobile broadband modems. โœจ It doesn't matter what protocol the actual device speaks (Generic AT, vendor-specific AT, QCDM, QMI, MBIM... the whole alphabet soup ๐Ÿ“), ModemManager handles it for you.

ModemManager is a DBus-based system daemon, so it's not meant to be used directly from the command line. ๐Ÿ™ˆ

bestie, seriously, don't go poking at it from your terminal like it's a normal app. It's a daemon. Let it do its thing in the background. ๐Ÿ’€

๐ŸŒธ APPLICATION OPTIONS ๐ŸŒธ

  • --filter-policy=<policy> โ€” this one decides which ports get probed and how ๐Ÿ”
    • 'ALLOWLIST-ONLY' โ€” only devices or ports that are explicitly allowlisted with the 'ID_MM_DEVICE_PROCESS' udev tag get probed
    • 'STRICT' โ€” only the TTY ports that are heuristically determined to be very likely modem ports get probed. It may end up ignoring some devices, so heads up ๐Ÿฅบ
  • --no-auto-scan โ€” fully disables the udev-based auto-scan that goes looking for devices ๐Ÿšซ
  • --initial-kernel-events=<filename> โ€” tells it where to find the file with the list of initial kernel events. The ModemManager daemon will process that file on startup ๐Ÿ“‚
  • --debug โ€” runs ModemManager with the "DEBUG" log level and without daemonizing. Super useful for debugging, because log output goes to your controlling terminal as well as syslog ๐Ÿ”ง
  • -V, --version โ€” prints the ModemManager software version and exits ๐Ÿท๏ธ
  • -h, --help โ€” shows the application options ๐Ÿ’โ€โ™€๏ธ

๐Ÿ“ LOGGING OPTIONS ๐Ÿ“

  • --log-level=<level> โ€” controls how much info ModemManager sends to the log destination (usually syslog's "daemon" facility). By default only informational, warning, and error messages get logged. Your level has to be one of "ERR", "WARN", "INFO" or "DEBUG" โญ
  • --log-file=<filename> โ€” picks a file to dump the log messages into, instead of syslog ๐Ÿ—‚๏ธ
  • --log-journal โ€” outputs log messages to the systemd journal ๐Ÿ““
  • --log-timestamps โ€” adds absolute timestamps to the log output ๐Ÿ•ฐ๏ธ
  • --log-relative-timestamps โ€” adds timestamps relative to the start time of the daemon to the log output โฑ๏ธ

๐Ÿงช TEST OPTIONS ๐Ÿงช

  • --test-session โ€” runs the ModemManager daemon on the Session bus instead of the System bus ๐ŸšŒ
  • --test-enable โ€” enables the Test DBus interface in the daemon ๐Ÿงš
  • --test-plugin-dir=[PATH] โ€” points the daemon at an alternate directory to look for vendor plugins in ๐Ÿ“

๐Ÿ‘‘ AUTHOR ๐Ÿ‘‘

Aleksander Morgado <aleksander@aleksander.es> ๐Ÿซถ

๐Ÿ”— SEE ALSO ๐Ÿ”—

mmcli(1), NetworkManager(8) ๐Ÿ’œ


okay that's the whole tea โ˜•๐Ÿ’– MODEMMANAGER(8) from 5 September 2014, and you now officially know more about modem daemons than most people. slay, bestie ๐Ÿ’…โœจ

๐Ÿ“ฆ where this page comes from