From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Interface friendly names for AF_INET6
Date: Thu, 10 Mar 2016 13:49:00 -0000 [thread overview]
Message-ID: <20160310134903.GC27354@calimero.vinschen.de> (raw)
In-Reply-To: <20160310133223.GB27354@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]
On Mar 10 14:32, Corinna Vinschen wrote:
> Hi Marco,
>
> On Mar 10 12:10, Marco Atzeri wrote:
> > I am trying to put a small interface info tool
> > to debug some hangs reported on openmpi.
> >
> > The aim is to produce something like
> >
> > {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23)
> > flags: up running multicast
> > address: <fe80::9953:b1f5:a643:4497%15>
> > Local Area Connection
> > {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET (2)
> > flags: up broadcast running multicast
> > address: <172.21.188.188>
> > Local Area Connection
> >
> > I am using getifaddrs to obtain all the AF_INET and AF_INET6
> > interface, however I can only obtain the friendly name of the
> > AF_INET using
> > ioctl(sock, SIOCGIFFRNDLYNAM
>
> getifaddrs should return the friendly name. Strruct ifall
> has a member ifa_frndlyname, type struct ifreq_frndlyname,
> which is filled for AF_INET and AF_INET6 interfaces.
Oh, I see. The friendlyname is there, but struct ifaddrs is missing a
pointer to it. That's the confusion you get when reusing the same
function and structure type for multiple APIs.
This could be easily rectified by utilizing the ifa_data pointer which
is unused so far. It could point to a structure pointing to the other
values collected but not yet exposed by getifaddrs, e.g.:
struct ifall_data
{
struct sockaddr ifa_hwaddr;
int ifa_metric;
int ifa_mtu;
int ifa_ifindex;
struct ifreq_frndlyname ifa_frndlyname;
};
ifa_data = pointer to ifall_data;
Would that help to get this into Cygwin 2.5.0?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-10 13:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 11:10 Marco Atzeri
2016-03-10 13:32 ` Corinna Vinschen
2016-03-10 13:49 ` Corinna Vinschen [this message]
2016-03-10 14:30 ` Marco Atzeri
2016-03-10 17:41 ` Corinna Vinschen
2016-05-13 15:00 ` Marco Atzeri
2016-05-20 16:45 ` Corinna Vinschen
2016-03-10 14:03 ` Corinna Vinschen
2016-03-10 14:35 ` Marco Atzeri
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=20160310134903.GC27354@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).