Creating an Ethernet subtype setting

Creating an Ethernet subtype setting

[Marcel Holtmann]

Hi guys,

so we have more and more subsystem that expose themselves as Ethernet
networking devices and it really becomes hard to identify them in an
easy way. For example WiFi has been an Ethernet device since a long time
now and distinguishing between Ethernet and WiFi is not that hard since
we have the good old WEXT ioctls to identify WiFi devices. However with
WiMAX, Bluetooth, GSM/CDMA modems and even Ethernet bridge devices, it
would be nice to have an easy way to identify them. Since it has become
a mess for laptops that include 4 or more different technologies.

For most of these Ethernet devices, we have to either connect first or
authenticate or do something via a control channel to make them work. So
it would be nice to have an easy way to identify them. I was thinking
about doing this on a per driver or subsystem level and just setting a
subtype value that is Linux specific. We could then expose this via
sysfs and HAL, DeviceKit and udev could use it to annotate these devices
correctly.

Is this is a good idea or totally stupid and should be done better on a
different level?

Regards

Marcel

Re: Creating an Ethernet subtype setting

[Lennert Buytenhek]

On Thu, Mar 26, 2009 at 01:41:58PM +0100, Marcel Holtmann wrote:

> so we have more and more subsystem that expose themselves as Ethernet
> networking devices and it really becomes hard to identify them in an
> easy way. For example WiFi has been an Ethernet device since a long time
> now and distinguishing between Ethernet and WiFi is not that hard since
> we have the good old WEXT ioctls to identify WiFi devices. However with
> WiMAX, Bluetooth, GSM/CDMA modems and even Ethernet bridge devices,

Also:
- VLAN interfaces
- TAP interfaces
- ETH_P_TEB
- (DSA interfaces)