All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Thode <mthode@mthode.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: getting a list of naked interface names from iproute2
Date: Tue, 17 Feb 2015 22:45:06 -0600	[thread overview]
Message-ID: <54E418D2.3020406@mthode.org> (raw)
In-Reply-To: <20150217102358.67b9d826@uryu.home.lan>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On 02/17/2015 09:23 AM, Stephen Hemminger wrote:
> On Mon, 16 Feb 2015 18:07:12 -0600
> Matthew Thode <mthode@mthode.org> wrote:
> 
>> iproute2 seems to like to add @ and : info to it's output.  This makes
>> parsing it hard for things like neutron (openstack).  I have a patch to
>> slightly update it (still missing some things, I'll link it at the end
>> if interested).  Is there a better way of getting interface names from
>> iproute2 without having to strip out at characters like '@' and ':'?
>>
>> changeset in neutron: https://review.openstack.org/#/c/154128/
>> link to current code:
>> https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ip_lib.py#L110-L131
>>
>> I'd appreciate your help, I'd rather not have to go through each link
>> type to pull it's delimiter, but if needed I guess it's needed.
>>
> 
> Stop screenscraping, and use a real API.
> All of the above would work better:
>   1. Libc if_nameindex
>   2. Legacy ioctl(SIOCGIFCONF)
>   3. Netlink  NLMMSG_REQ (RTM_GETLINK)
>   4. Sysfs /sys/class/net
> 
Do you happen to know a way to request it for a specific namespace?
going over the links in /sys/class/net only gets you the current
namespace (was the easiest method to do in python2.7).

-- 
Matthew Thode


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2015-02-18  4:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  0:07 getting a list of naked interface names from iproute2 Matthew Thode
2015-02-17 15:23 ` Stephen Hemminger
2015-02-18  4:45   ` Matthew Thode [this message]
2015-02-18 18:55     ` Cong Wang

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=54E418D2.3020406@mthode.org \
    --to=mthode@mthode.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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.