From: Patrick McHardy <kaber@trash.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Pavel Emelianov <xemul@openvz.org>,
David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Kirill Korotaev <dev@openvz.org>,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH] Virtual ethernet tunnel (v.2)
Date: Mon, 11 Jun 2007 13:42:57 +0200 [thread overview]
Message-ID: <466D3541.8020904@trash.net> (raw)
In-Reply-To: <46682976.8050904@candelatech.com>
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).
prev parent reply other threads:[~2007-06-11 11:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 11:13 [PATCH] Virtual ethernet tunnel (v.2) Pavel Emelianov
2007-06-07 11:16 ` [PATCH] Module for ip utility to support veth device (v.2) Pavel Emelianov
2007-06-07 15:59 ` Stephen Hemminger
2007-06-07 15:23 ` [PATCH] Virtual ethernet tunnel (v.2) Ben Greear
2007-06-07 15:39 ` Pavel Emelianov
2007-06-07 15:51 ` Ben Greear
2007-06-07 16:04 ` Pavel Emelianov
2007-06-07 16:35 ` Ben Greear
2007-06-08 16:00 ` Pavel Emelianov
2007-06-08 17:00 ` Ben Greear
2007-06-08 19:49 ` Carl-Daniel Hailfinger
2007-06-08 23:46 ` Ben Greear
2007-06-11 11:42 ` Patrick McHardy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466D3541.8020904@trash.net \
--to=kaber@trash.net \
--cc=containers@lists.osdl.org \
--cc=davem@davemloft.net \
--cc=dev@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.