Received: with ECARTIS (v1.0.0; list netdev); Thu, 11 Mar 2004 08:54:49 -0800 (PST) Received: from mx1.redhat.com (mx1.redhat.com [66.187.233.31]) by oss.sgi.com (8.12.10/8.12.9) with SMTP id i2BGshKO015481 for ; Thu, 11 Mar 2004 08:54:44 -0800 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i2BGse07029134; Thu, 11 Mar 2004 11:54:40 -0500 Received: from lacrosse.corp.redhat.com (lacrosse.corp.redhat.com [172.16.52.154]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2BGse805348; Thu, 11 Mar 2004 11:54:40 -0500 Received: from localhost (mgalgoci@localhost) by lacrosse.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2BGseu24397; Thu, 11 Mar 2004 11:54:40 -0500 X-Authentication-Warning: lacrosse.corp.redhat.com: mgalgoci owned process doing -bs Date: Thu, 11 Mar 2004 11:54:40 -0500 (EST) From: Matthew Galgoci X-X-Sender: mgalgoci@lacrosse.corp.redhat.com To: James Ketrenos cc: netdev@oss.sgi.com Subject: Re: Device naming for wireless NICs... In-Reply-To: <405093A7.90209@linux.co.intel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 3940 X-ecartis-version: Ecartis v1.0.0 Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com X-original-sender: mgalgoci@redhat.com Precedence: bulk X-list: netdev Content-Length: 1627 Lines: 37 On Thu, 11 Mar 2004, James Ketrenos wrote: > > If this topic been hashed a lot already, please let me know the keywords I might > search for in the archives to find the threads. > > I've had a few requests by users of the IPW2100 wireless driver to switch the > default interface name to be wlanX vs. ethX. In my prior searches through the > wireless drivers in the 2.6.3 kernel tree, I couldn't find any that changed from > the default. > > I don't mind adding a module parameter to change the default name (if that is > the standard practice), but thought I'd see what others thing rather than just > going off and doing something random. > > Is there a technical or ease of use reason switching away from ethX? My > thinking in keeping it eth was that it then represents a greater chance of "just > working" with most networking scripts and utilities that may assume ethX is the > interface name. TBH I don't think it much matters. I know that at least Red Hat's networking scripts (and possibly other distributions) did at one point assume that each interface would be named ethX, but I don't think that is the case anymore. Some drivers even present both a wlanX and an ethX interface, which I think is an atavism that goes back to networking scripts breaking horribly on non-ethX interface names. Going forward it might be worth while to standardize all wireless interface names, just to show at a glance that an interface is 802.11x, and also to differentiate the fact that eventually 802.11 will be its own network stack. -- Matthew Galgoci System Administrator Red Hat, Inc 919.754.3700 x44155