public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Ethernet interface names with cygwin 1.7.5
Date: Mon, 09 Aug 2010 09:36:00 -0000	[thread overview]
Message-ID: <20100809093552.GA17038@calimero.vinschen.de> (raw)
In-Reply-To: <OF47560A7F.E0551056-ONC125777A.0031B63E-C125777A.0031C19F@atlascopco.com>

On Aug  9 11:03, laurent.metais@cp.com wrote:
> I am using a very simple to find all ethernet on my PC with cygwin :
> [...]
> With cygwin 1.7.5 the result is :
> $ ./a.exe
> Interfaces (count = 5):
>         {EE0A9E93-9A06-4CCB-B957-074C921D39FB}
>         {46D151B0-33BB-4706-A450-B29F50F8095A}
>         {B9BDEE37-C781-447B-B457-D4B17C576948}
>         {A46ED7E6-A8A7-431E-BDE0-68DBEA2D334D}
>         MS TCP Loopback interface
> 
> with release 1.5.25, the result was using the well-known names (lo0, eth0, 
> eth1, etc...).
> 
> How can retrieve the standard names with release 1.7.5 ? Is it a new 
> naming convention ?

The problem with the well-known names is that they are not guaranteed to
be unique, because the order of the interfaces returned by the Windows
API can change arbitrarily.
Therefore Cygwin 1.7 starts to return the really unique Win32 interface
names, which are the above UUID-based names (plus the old "MS TCP Loopback"
name).

The uniqueness of the interface name is quite important in a couple of
circumstances, so, starting wit Windows XP, there's no way anymore to
retrieve the old well-known names since they are just not generated.

What's left is a Cygwin-specific extension, the SIOCGIFFRNDLYNAM ioctl,
which is documented in /usr/include/cygwin/if.h, see the comment
preceeding the definition of IFRF_FRIENDLYNAMESIZ.  This extension
returns the so-called "FriendlyName", which is the interface name as
shown in the Windows network properties.

Btw., Cygwin 1.7 also has the getifaddrs/freeifaddrs API to retrieve
the interface list (and the /proc/net/if_inet6 file).


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2010-08-09  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  9:03 laurent.metais
2010-08-09  9:36 ` Corinna Vinschen [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=20100809093552.GA17038@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).