netdev
[Top] [All Lists]

Device naming for wireless NICs...

Subject: Device naming for wireless NICs...
From: James Ketrenos <jketreno@xxxxxxxxxxxxxxxxxx>
Date: Thu, 11 Mar 2004 10:28:23 -0600
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20040311031709.GC3782@jm.kir.nu>
References: <20040304023524.GA19453@bougret.hpl.hp.com> <20040310165548.A24693@infradead.org> <20040310172114.GA8867@bougret.hpl.hp.com> <404F5097.4040406@pobox.com> <20040310175200.GA9531@bougret.hpl.hp.com> <404F5744.1040201@pobox.com> <20040311024816.GC3738@jm.kir.nu> <404FD6BC.7090409@pobox.com> <20040311031709.GC3782@jm.kir.nu>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

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.

Thanks,
James

<Prev in Thread] Current Thread [Next in Thread>