delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/04/21/13:50:09

X-Spam-Check-By: sourceware.org
Message-ID: <44491B3E.5090506@nrl.navy.mil>
Date: Fri, 21 Apr 2006 13:49:50 -0400
From: Ian <ian DOT downard AT nrl DOT navy DOT mil>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: network interface names
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

How does cygwin's eth(whatever) relate to the windows interface names?

For example, on my laptop, eth0 is tied to my wireless network 
connection and eth1 is tied to my wired local area connection.

I'm developing DHCP software for cygwin, and I need to be able to derive 
the cygwin network interface name (e.g. eth0, or eth1...) given either 
the connection's MAC address, its IP address, or its windows interface 
name (e.g. "Local Area Connection", or "Gigabit Integrated Controller", 
or "WLAN Mini-PCI Card #2", or something like).

Thanks for any help,
  Ian

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019