On Sun, Jan 5, 2014 at 8:44 PM, Marcel Holtmann <[email protected]> wrote: >> Hm, I thought that was to fix false negatives. I.e., that some devices >> with, say, DEVTYPE=bluetooth should in fact be treated as regular >> ethernet? > > DEVTYPE=bluetooth and DEVTYPE=wlan are not false negatives. They should be > like that. That is something current userspace relies on. We can not break > this. > > However you will see a DEVTYPE=bluetooth as Ethernet emulation and another as > raw IP (6loWPAN). You want to differentiate these for the default address > assignment you pick. For example 6loWPAN will just rely on IPv6 route > solicitation. > > Same applies to DEVTYPE=wwan btw. Some Qualcomm cards can be exposed as > Ethernet or they do a raw IP only header in their netdev. DEVTYPE is just to > figure out the underlying technology of your network device. Then the ARPHRD_ > is to get an idea of the actual encapsulation that is used.
Thanks for the explanation. This fits what my expectations. So what we are interested in is purely to match on the technology, and not on the encapsulation. That would have to be a separate key, if it turns out to be interesting (which it may very well do). Cheers, Tom _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
