netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: netdev@oss.sgi.com, James Ketrenos <jketreno@linux.co.intel.com>
Subject: Re: Device naming for wireless NICs...
Date: Thu, 11 Mar 2004 10:22:04 -0800	[thread overview]
Message-ID: <20040311182204.GA5989@bougret.hpl.hp.com> (raw)

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.

	This is my personal rule of thumb :
	o if the interface use Ethernet frames (i.e. offer Ethernet
emulation), then it should be name 'ethX'.
	o if the interface use 802.11 frames (rawe/native), it should
use 'wifiX'.

	The Aironet driver is a good example of this, for each
hardware it offers two interfaces, 'ethX' and 'wifiY'.
	Personally, I've been converting a few drivers to use 'ethX'
and removing 'wlanX' hacks where I saw them..

> 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.

	Just point them to :
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/HOTPLUG.txt

> 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.

	Note that the RedHat graphical configuration tool (neat) seems
to insist on only using 'ethX' names. Yes, only using 'ethX' is
generally safer (principle of least surprise).

	Have fun...

	Jean

             reply	other threads:[~2004-03-11 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11 18:22 Jean Tourrilhes [this message]
2004-03-11 19:33 ` Device naming for wireless NICs Matthew Galgoci
2004-03-11 19:47   ` Jean Tourrilhes
  -- strict thread matches above, loose matches on Subject: below --
2004-03-04  2:35 [PATCH 2.6] Intersil Prism54 wireless driver Jean Tourrilhes
2004-03-10 16:55 ` Christoph Hellwig
2004-03-10 17:21   ` Jean Tourrilhes
2004-03-10 17:29     ` Jeff Garzik
2004-03-10 17:52       ` Jean Tourrilhes
2004-03-10 17:58         ` Jeff Garzik
2004-03-11  2:48           ` Jouni Malinen
2004-03-11  3:02             ` Jeff Garzik
2004-03-11  3:17               ` Jouni Malinen
2004-03-11 16:28                 ` Device naming for wireless NICs James Ketrenos
2004-03-11 16:36                   ` Tomasz Torcz
2004-03-11 16:54                   ` Matthew Galgoci
2004-03-11 18:25                     ` Jeff Garzik
2004-03-11 18:23                   ` Jeff Garzik
2004-03-12 10:30                     ` P

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040311182204.GA5989@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=jketreno@linux.co.intel.com \
    --cc=jt@hpl.hp.com \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).