X-Spam-Check-By: sourceware.org Date: Wed, 3 Jan 2007 11:38:41 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Cygwin's ioctl(SIOCGIFFLAGS) always sets the IFF_UP flag Message-ID: <20070103103841.GB11943@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <17812.8696.611370.458886@metro-north.cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17812.8696.611370.458886@metro-north.cs.columbia.edu> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Dec 28 14:58, Jonathan Lennox wrote: > I've discovered that Cygwin's ioctl(SIOCGIFFLAGS) call always sets the > IFF_UP flag, even if the interface being queried is disabled or > unconfigured. Yes, right. SIOCGIFFLAGS is just faked to handle the default case. See fhandler_socket::ioctl(), it doesn't even call get_ifconf in case of SIOCGIFFLAGS. The code is older than the advent of get_2k_ifconf, AFAIR. Hmm, it shouldn't be too hard to support SIOCGIFFLAGS more or less correctly starting with Windows 2000. I put this on my TODO list. Thanks for the report, 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/