X-Spam-Check-By: sourceware.org Date: Fri, 21 Apr 2006 22:39:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: network interface names Message-ID: <20060421203920.GA27541@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <44491B3E DOT 5090506 AT nrl DOT navy DOT mil> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44491B3E.5090506@nrl.navy.mil> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Apr 21 13:49, Ian wrote: > How does cygwin's eth(whatever) relate to the windows interface names? Grab the Cygwin sources, unpack and have a look into the file winsup/cygwin/net.cc, functions get_2k_ifconf, get_nt_ifconf and get_95_ifconf. It's basically just enumerating as the interfaces come along, using either direct registry access or the GetIpAddrTable function. Should be pretty simple to read. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/