{"id":3241,"date":"2022-12-20T16:43:56","date_gmt":"2022-12-20T19:43:56","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/modemmanager-man8\/"},"modified":"2022-12-20T16:43:56","modified_gmt":"2022-12-20T19:43:56","slug":"modemmanager-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/modemmanager-man8\/","title":{"rendered":"MODEMMANAGER (man8)"},"content":{"rendered":"<h1 align=\"center\">MODEMMANAGER<\/h1>\n<p> <a href=\"#NAME\">NAME<\/a><br \/> <a href=\"#SYNOPSIS\">SYNOPSIS<\/a><br \/> <a href=\"#DESCRIPTION\">DESCRIPTION<\/a><br \/> <a href=\"#APPLICATION OPTIONS\">APPLICATION OPTIONS<\/a><br \/> <a href=\"#LOGGING OPTIONS\">LOGGING OPTIONS<\/a><br \/> <a href=\"#TEST OPTIONS\">TEST OPTIONS<\/a><br \/> <a href=\"#AUTHOR\">AUTHOR<\/a><br \/> <a href=\"#SEE ALSO\">SEE ALSO<\/a> <\/p>\n<hr>\n<h2>NAME <a name=\"NAME\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">ModemManager \u2212 mobile broadband modem management daemon<\/p>\n<h2>SYNOPSIS <a name=\"SYNOPSIS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>ModemManager<\/b> [<i>OPTION<\/i>&#8230;]<\/p>\n<h2>DESCRIPTION <a name=\"DESCRIPTION\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">ModemManager provides a unified high level API for communicating with mobile broadband modems, regardless of the protocol used to communicate with the actual device (Generic AT, vendor-specific AT, QCDM, QMI, MBIM&#8230;).<\/p>\n<p style=\"margin-left:11%; margin-top: 1em\">ModemManager is a DBus-based system daemon and is not meant to be used directly from the command line.<\/p>\n<h2>APPLICATION OPTIONS <a name=\"APPLICATION OPTIONS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>\u2212\u2212filter\u2212policy=<policy><\/b><\/p>\n<p style=\"margin-left:22%;\">Specify which ports are probed and how:<\/p>\n<p style=\"margin-left:25%;\"><b>\u2019WHITELIST-ONLY\u2019<\/b><\/p>\n<p style=\"margin-left:35%;\">Only devices or ports explicitly whitelisted with the \u2019ID_MM_DEVICE_PROCESS\u2019 udev tag are probed.<\/p>\n<p style=\"margin-left:25%;\"><b>\u2019DEFAULT\u2019<\/b><\/p>\n<p style=\"margin-left:35%;\">All ports are allowed to be probed except for the ones explicitly greylisted as RS232 adapters or completely blacklisted.<\/p>\n<p style=\"margin-left:25%;\"><b>\u2019STRICT\u2019<\/b><\/p>\n<p style=\"margin-left:35%;\">Only the TTY ports that are heurstically determined to be very likely to be modem ports are probed. Nay end up ignoring some devices.<\/p>\n<p style=\"margin-left:25%;\"><b>\u2019PARANOID\u2019<\/b><\/p>\n<p style=\"margin-left:35%;\">This is equivalent to running the STRICT mode but also applying the blacklist and RS232 greylist filters explicitly.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212no\u2212auto\u2212scan<\/b><\/p>\n<p style=\"margin-left:22%;\">Fully disable udev-based auto-scan looking for devices.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212initial\u2212kernel\u2212events=<filename><\/b><\/p>\n<p style=\"margin-left:22%;\">Specify location of the file where the list of initial kernel events is available. The ModemManager daemon will process this file on startup.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212debug<\/b><\/p>\n<p style=\"margin-left:22%;\">Runs ModemManager with &#8220;DEBUG&#8221; log level and without daemonizing. This is useful for debugging, as it directs log output to the controlling terminal in addition to syslog.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212V, \u2212\u2212version<\/b><\/p>\n<p style=\"margin-left:22%;\">Print the ModemManager software version and exit.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212h, \u2212\u2212help<\/b><\/p>\n<p style=\"margin-left:22%;\">Show application options.<\/p>\n<h2>LOGGING OPTIONS <a name=\"LOGGING OPTIONS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>\u2212\u2212log\u2212level=<level><\/b><\/p>\n<p style=\"margin-left:22%;\">Sets how much information ModemManager sends to the log destination (usually syslog\u2019s &#8220;daemon&#8221; facility). By default, only informational, warning, and error messages are logged. Given level must be one of &#8220;ERR&#8221;, &#8220;WARN&#8221;, &#8220;INFO&#8221; or &#8220;DEBUG&#8221;.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212log\u2212file=<filename><\/b><\/p>\n<p style=\"margin-left:22%;\">Specify location of the file where ModemManager will dump its log messages, instead of syslog.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212log\u2212journal<\/b><\/p>\n<p style=\"margin-left:22%;\">Output log message to the systemd journal.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212log\u2212timestamps<\/b><\/p>\n<p style=\"margin-left:22%;\">Include absolute timestamps in the log output.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212log\u2212relative\u2212timestamps<\/b><\/p>\n<p style=\"margin-left:22%;\">Include timestamps, relative to the start time of the daemon, in the log output.<\/p>\n<h2>TEST OPTIONS <a name=\"TEST OPTIONS\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>\u2212\u2212test\u2212session<\/b><\/p>\n<p style=\"margin-left:22%;\">Run the ModemManager daemon in the Session bus instead of the System bus.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212test\u2212enable<\/b><\/p>\n<p style=\"margin-left:22%;\">Enable the Test DBus interface in the daemon.<\/p>\n<p style=\"margin-left:11%;\"><b>\u2212\u2212test\u2212plugin\u2212dir=[PATH]<\/b><\/p>\n<p style=\"margin-left:22%;\">Specify an alternate directory where the daemon should look for vendor plugins.<\/p>\n<h2>AUTHOR <a name=\"AUTHOR\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\">Aleksander Morgado <aleksander@aleksander.es><\/p>\n<h2>SEE ALSO <a name=\"SEE ALSO\"><\/a> <\/h2>\n<p style=\"margin-left:11%; margin-top: 1em\"><b>mmcli<\/b>(1), <b>NetworkManager<\/b>(8)<\/p>\n<hr>\n","protected":false},"excerpt":{"rendered":"<p>  ModemManager \u2212 mobile broadband modem management daemon <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,378],"class_list":["post-3241","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-modemmanager"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3241","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3241"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3241\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3241"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3241"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3241"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}