[systemd-bugs] [Bug 70832] New: Udev should not blacklist DEVTYPE changes in rules

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Oct 24 11:10:11 CEST 2013


https://bugs.freedesktop.org/show_bug.cgi?id=70832

          Priority: medium
            Bug ID: 70832
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Udev should not blacklist DEVTYPE changes in rules
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: juho.ostman at gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

A couple of USB-attached mobile broadband routers can be used either as a modem
or as a network interface. If the device is employed as a network interface, it
suffices to ask for IP settings via DHCP, and no other initialization is
necessary.

The kernel driver assigns the DEVTYPE "wwan" for these devices, and this
information is used by NetworkManager, for example, to decide which user-mode
driver should be chosen to configure the interface. If the DEVTYPE is "wwan",
the device is treated as a modem, on the other hand, if the DEVTYPE is "eth" or
some unrecognized string, the interface is configured as a network interface.

I have used an udev rule like this to select the correct behaviour:
SUBSYSTEM=="net", ATTRS{idVendor}=="1199", ATTRS{idProduct}=="68a3",
ENV{ID_MM_CANDIDATE}="0", ENV{DEVTYPE}="eth"

Changing the DEVTYPE in a udev rule is the simplest way to choose how a device
should be configured. Actually, NetworkManager does not currently provide any
other way to affect the decision. Therefore, changing the DEVTYPE should not be
blacklisted.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20131024/78c7be00/attachment.html>


More information about the systemd-bugs mailing list