Thread (8 messages) 8 messages, 4 authors, 2014-12-12

Re: [PATCH v3] wireless: Supporting of IFLA_INFO_KIND rtnl attribute

From: <hidden>
Date: 2014-12-09 23:32:55

On Wed, Dec 10, 2014 at 12:23:14AM +0100, Marcel Holtmann wrote:
Hi Johannes,
quoted
On Dec 9, 2014, at 23:21, Vadim Kochan [off-list ref] wrote:

It allows to identify the wlan kind of device for the user application,
e.g.:

   # ip -d link

   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
       link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0
   2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
       link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff promiscuity 0
   3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
       link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff promiscuity 0
       wlan
have we considered also exposing the mode of this netdev. So for example sta,ap,p2p-go,p2p-client etc. If we can send dynamic updates via RTNL, we could easily tell the networking management system what type of wireless device we have here. I am thinking about it like "wlan/p2p-go" etc. Or should this be better kept strictly to "wlan".

And I am not sure RTNL would be capable of changing this kind strings at runtime anyway.

Regards

Marcel
May be better do not mix 2 things in one attribute?

Regards,
Vadim
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help