[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <466D3541.8020904@trash.net>
Date: Mon, 11 Jun 2007 13:42:57 +0200
From: Patrick McHardy <kaber@...sh.net>
To: Ben Greear <greearb@...delatech.com>
CC: Pavel Emelianov <xemul@...nvz.org>,
David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Daniel Lezcano <dlezcano@...ibm.com>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Kirill Korotaev <dev@...nvz.org>,
Linux Containers <containers@...ts.osdl.org>
Subject: Re: [PATCH] Virtual ethernet tunnel (v.2)
Ben Greear wrote:
> Pavel Emelianov wrote:
>
>>> I would also like some way to identify veth from other device types,
>>> preferably
>>> something like a value in sysfs. However, that should not hold up
>>>
>>
>>
>> We can do this with ethtool. It can get and print the driver name of
>> the device.
>>
>
> I think I'd like something in sysfs that we could query for any
> interface. Possible return
> strings could be:
> VLAN
> VETH
> ETH
> PPP
> BRIDGE
> AP /* wifi access point interface */
> STA /* wifi station */
> ....
>
> I will cook up a patch for consideration after veth goes in.
The rtnl_link API gives you the name of the driver (IFLA_INFO_KIND).
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists