From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261799AbTKOQWl (ORCPT ); Sat, 15 Nov 2003 11:22:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261812AbTKOQWl (ORCPT ); Sat, 15 Nov 2003 11:22:41 -0500 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:64478 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S261799AbTKOQWk (ORCPT ); Sat, 15 Nov 2003 11:22:40 -0500 Message-ID: <3FB652BA.1010905@pobox.com> Date: Sat, 15 Nov 2003 11:22:18 -0500 From: Jeff Garzik User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: azarah@nosferatu.za.org CC: Linux Kernel Mailing Lists Subject: Re: Carrier detection for network interfaces References: <1068912989.5033.32.camel@nosferatu.lan> In-Reply-To: <1068912989.5033.32.camel@nosferatu.lan> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Martin Schlemmer wrote: > Is there any proper way to detect a carrier signal with network > interfaces ? I have recently come across a problem where we tried > to do with with checking for 'RUNNING', which do not work for all > drivers, as well as mii-tool that fails in some cases. What kernel version? In 2.6 you have linkwatch. In 2.4 and 2.6, you have ETHTOOL_GLINK, and mii-tool. Jeff