From: "David S. Miller" <davem@redhat.com>
To: wjhun@cisco.com
Cc: greearb@candelatech.com, netdev@oss.sgi.com
Subject: Re: Getting details about an 802.1q VLAN interface from userspace
Date: Mon, 17 Feb 2003 18:29:15 -0800 (PST) [thread overview]
Message-ID: <20030217.182915.41644338.davem@redhat.com> (raw)
In-Reply-To: <20030213143921.A21977@cisco.com>
From: Will Jhun <wjhun@cisco.com>
Date: Thu, 13 Feb 2003 14:39:21 -0800
Is there a better way to get this information via netlink or some
ioctl()? Would it be useful if I (or someone) added an ioctl() type to
get information about a VLAN interface? (vlan, ifindex of trunking
(real_dev) interface, priority maps; basically the content of struct
vlan_dev_info)
I would accept new netlink interfaces to get and set this
information. ioctls are gross and will not be tolerated :)
next prev parent reply other threads:[~2003-02-18 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 22:39 Getting details about an 802.1q VLAN interface from userspace Will Jhun
2003-02-18 2:29 ` David S. Miller [this message]
2003-02-19 2:48 ` jamal
2003-02-19 3:13 ` David S. Miller
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=20030217.182915.41644338.davem@redhat.com \
--to=davem@redhat.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.com \
--cc=wjhun@cisco.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).