Seems like MM_FILTER_RULE_TTY_WITH_NET overrides ID_MM_DEVICE_IGNORE

[Aleksander Morgado]

Hey Menno,

> > After many hours we finally found out ModemManager is probing the devices, so we added the udev rules:
> >
> > /etc/udev/rules.d/78-custom-mm-blacklist-internal-modem.rules :
> >
> > ACTION!="add|change|move", GOTO="custom_mm_blacklist_internal_modem_end"
> > ATTRS{idVendor}=="[redacted1]" ATTRS{idProduct}=="[redacted2]", ENV{ID_MM_DEVICE_IGNORE}="1"
> > ATTRS{idVendor}=="[redacted1]" ATTRS{idProduct}=="[redacted3]", ENV{ID_MM_DEVICE_IGNORE}="1"
> > LABEL="custom_mm_blacklist_internal_modem_end"
> >
> > but looking at the logs I see:
> >
> > ModemManager[3751]: <debug> [filter] (tty/ttyACM0): port filtered: device is blocklisted
> > ModemManager[3751]: <debug> [filter] (net/enxd[redacted4]) port allowed: net device
> > ModemManager[3751]: <debug> [filter] (net/enxd[redacted4]) port allowed: net device
> > ModemManager[3751]: <debug> [filter] (tty/ttyACM0): port allowed: device also exports a net interface
> >
> > So if ModemManager successfully found the device is blocklisted, why does it continue to probe the port?
>
> This is definitely a bug. I've opened
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/833
>

We've been trying to get an idea of why this issue is happening in
your setup but it's not really clear.
Would you be able to send a full MM debug log
(https://modemmanager.org/docs/modemmanager/debugging/#daemon-debug-logs)
and share a bit more about your system? e.g. is it openwrt based or
not, the output of "usb-devices" and "lsusb -v" for this device...

Thanks

-- 
Aleksander