FS#58351 - [modemmanager] Modem doesn't recognised when the strict filter policy patch applied

Attached to Project: Arch Linux
Opened by Balló György (City-busz) - Wednesday, 25 April 2018, 08:40 GMT
Last edited by Jan de Groot (JGC) - Saturday, 19 May 2018, 21:23 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please don't apply the 'strict-filter.diff' patch, because it against me to use my USB modem with ModemManager.


My hardware is:
Bus 002 Device 015: ID 19d2:0117 ZTE WCDMA Technologies MSM


When strict-filter.diff patch is applied, I get this error, and ModemManager doesn't recognize the modem:

Apr 25 10:13:16 arch ModemManager[3301]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0': not supported by any plugin
Apr 25 10:13:16 arch ModemManager[3301]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:04:00.0': not supported by any plugin


When strict-filter.diff patch is not applied, ModemManager recognize the modem, and I can use NetworkManager to connect:

Apr 25 10:04:56 arch ModemManager[2693]: <info> [device /sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb2/2-1] creating modem with plugin 'ZTE' and '3' ports
Apr 25 10:04:56 arch ModemManager[2693]: <info> Modem for device '/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb2/2-1' successfully created
Apr 25 10:04:59 arch ModemManager[2693]: <warn> couldn't load Supported Modes: 'Couldn't retrieve supported modes'
Apr 25 10:04:59 arch ModemManager[2693]: <warn> couldn't load Supported IP families: 'Unknown error'
Apr 25 10:04:59 arch ModemManager[2693]: <info> Modem: state changed (unknown -> locked)
Apr 25 10:04:59 arch ModemManager[2693]: <warn> couldn't load IMSI: 'Unknown error'
Apr 25 10:04:59 arch ModemManager[2693]: <warn> couldn't load Operator identifier: 'Cannot load Operator ID without IMSI'
Apr 25 10:04:59 arch ModemManager[2693]: <warn> couldn't load list of Own Numbers: 'Failed to parse NV MDN command result: -17'
Apr 25 10:04:59 arch NetworkManager[410]: <warn> [1524643499.7494] modem["ttyUSB2"]: cannot enable/disable modem: locked
Apr 25 10:04:59 arch NetworkManager[410]: <info> [1524643499.7519] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/7)
Apr 25 10:04:59 arch NetworkManager[410]: <info> [1524643499.7529] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 25 10:04:59 arch NetworkManager[410]: <info> [1524643499.7536] device (ttyUSB2): modem state 'locked'
Apr 25 10:04:59 arch NetworkManager[410]: <info> [1524643499.7555] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Apr 25 10:05:05 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
Apr 25 10:05:08 arch ModemManager[2693]: <warn> couldn't load UE mode of operation for EPS: 'Unknown error'
Apr 25 10:05:08 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
Apr 25 10:05:08 arch NetworkManager[410]: <info> [1524643508.9762] modem["ttyUSB2"]: modem state changed, 'locked' --> 'disabled' (reason: unknown)
Apr 25 10:05:08 arch NetworkManager[410]: <info> [1524643508.9765] modem["ttyUSB2"]: modem state changed, 'disabled' --> 'enabling' (reason: user preference)
Apr 25 10:05:08 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
Apr 25 10:05:12 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
Apr 25 10:05:12 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
Apr 25 10:05:13 arch ModemManager[2693]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
Apr 25 10:05:13 arch NetworkManager[410]: <info> [1524643513.0748] modem["ttyUSB2"]: modem state changed, 'enabling' --> 'registered' (reason: user-requested)
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 19 May 2018, 21:23 GMT
Reason for closing:  Won't implement
Additional comments about closing:  The strict policy is wanted, as we don't want to send random commands to all serial ports by default.
Comment by Jan de Groot (JGC) - Wednesday, 25 April 2018, 09:04 GMT
Reverting to the default policy will make modemmanager send random commands to each and every serial port that it finds on the system. This is unwanted behavior.

If your modem doesn't work with the policy we set, you can add it to the whitelist:
https://www.freedesktop.org/software/ModemManager/api/1.8.0/ref-overview-modem-filter.html

Comment by Ihor (Ihorko) - Saturday, 19 May 2018, 08:14 GMT
I can't use my Nokia 6021 phone as bluetooth modem with this patch. If it's not enabled by default upstream due to not fully updated udev rules and this causes connection issues for existing users why do you enable it during compilation? As far as I understand it could be enabled by adding application parameter --filter-policy=STRICT.
Hope to see updated package soon.
Comment by Ihor (Ihorko) - Saturday, 19 May 2018, 10:04 GMT
Finally found workaround for whilelist in my case. /etc/udev/rules.d/77-mm-whitelist-rfcomm-modem.rules:
ACTION=="add|change|move", KERNEL=="rfcomm*", DEVPATH!="*/virtual/*", SUBSYSTEM=="tty", ENV{ID_MM_DEVICE_PROCESS}="1"

Loading...