udev rules messed up?

[Aleksander Morgado]

On 26/01/14 19:20, Aleksander Morgado wrote:
> I was just testing with all my devices targeting a 1.2 release, when I
> found out that the NDISDUP flags for Huawei devices were not being set
> properly. The tag setting logic just goes like this:
> 
> SUBSYSTEMS=="usb", ATTRS{bInterfaceClass}=="02",
> ATTRS{bInterfaceSubClass}=="06",ATTRS{bInterfaceProtocol}=="00",
> ENV{ID_MM_HUAWEI_NDISDUP}="1"
> 
> After digging a bit in the issue, I found (using ./test/lsudev net) that
> upon receiving the udev "add" event it correctly shows the tag we're
> looking for in the net device, but just after that we get a "move"
> event, where the tag is gone. See both events here, look for "ID_MM".
> 
> Any idea anyone? Why is that second 'move' event happening?


I think I just missed to add the "move" event to the udev rules, will
fix that.

-- 
Aleksander