From: Jouni Malinen <j@w1.fi>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeroen Vreeken <pe1rxq@amsat.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 15/16] use-regular-eth-suffix.diff
Date: Sun, 1 Apr 2007 18:40:03 -0700 [thread overview]
Message-ID: <20070402014003.GS16197@jm.kir.nu> (raw)
In-Reply-To: <Pine.LNX.4.61.0704012010530.12316@yvahk01.tjqt.qr>
On Sun, Apr 01, 2007 at 08:18:12PM +0200, Jan Engelhardt wrote:
> Some radio adapter drivers wrongly(?) name their devices "wlan%d"
> instead of "eth%d" (if you ask me, it should be %u - but not today).
> Technically, they operate like Ethernet, and in fact, running
> `/sbin/ip a` shows "link/ether" instead of "link/ieee80211".
The address may look like wired Ethernet (both are based on IEEE 802
standards), but IEEE 802.11 does not behave like IEEE 802.3. For
example, one cannot send frames with a foreign source address in client
mode when using IEEE 802.11 which is clearly different from wired
Ethernet. IEEE 802.11 interfaces (in client mode) cannot be bridged at
layer 2 in the same way as wired Ethernet interfaces could.
> This patch renames them back, but I would appreciate some comment,
> explanation or at least link why they actually have wlan%d there.
Renames _back_? No it doesn't. Host AP driver has never used eth%d as
the interface name template
> Index: linux-2.6.21-rc5/drivers/net/wireless/hostap/hostap_hw.c
> -static char dev_template[16] = "wlan%d";
> +static char dev_template[16] = "eth%d";
NAK. Host AP driver has been using wlan%d for close to seven years and I
see no reason to change it now. This will just cause problems for users.
If someone wants to rename the interface to something else, they can do
it with number of different ways from user space. The kernel default
should not be changed at this point.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2007-04-02 1:47 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 18:13 [PATCH 0/16] Assorted patches Jan Engelhardt
2007-04-01 18:13 ` [PATCH 1/16] vt-sysfs-for-colors.diff Jan Engelhardt
2007-04-02 6:49 ` Antonino A. Daplas
2007-04-02 7:31 ` [PATCH 17/16] Do not reset UTF8 on terminal reset Jan Engelhardt
2007-04-02 9:30 ` Antonino A. Daplas
2007-04-02 11:26 ` Paul LeoNerd Evans
2007-04-02 11:44 ` Antonino A. Daplas
2007-04-02 11:54 ` Paul LeoNerd Evans
2007-04-02 12:47 ` Antonino A. Daplas
2007-04-02 13:20 ` Paul LeoNerd Evans
2007-04-02 13:34 ` Jan Engelhardt
2007-04-02 18:50 ` Pavel Machek
2007-04-01 18:14 ` [PATCH 2/16] vt-pure-colors.diff Jan Engelhardt
2007-04-01 18:39 ` James Bruce
2007-04-02 6:49 ` Antonino A. Daplas
2007-04-02 7:04 ` Jan Engelhardt
2007-04-02 7:50 ` Antonino A. Daplas
2007-04-02 8:01 ` Jan Engelhardt
2007-04-01 18:14 ` [PATCH 3/16] vt-underline-color.diff Jan Engelhardt
2007-04-02 5:37 ` Andrew Morton
2007-04-02 6:57 ` Antonino A. Daplas
2007-04-01 18:14 ` [PATCH 4/16] vt-printk-color.diff Jan Engelhardt
2007-04-01 18:14 ` [PATCH 5/16] fix-kthread-niceness.diff Jan Engelhardt
2007-04-02 5:39 ` Andrew Morton
2007-04-01 18:15 ` [PATCH 06/16] isofs-add-write-bit.diff Jan Engelhardt
2007-04-01 18:15 ` [PATCH 07/16] kconfig-dynamic-frequency.diff Jan Engelhardt
2007-04-01 18:39 ` Kyle Moffett
2007-04-01 18:42 ` Jan Engelhardt
2007-04-01 18:52 ` Kyle Moffett
2007-04-01 19:01 ` Jan Engelhardt
2007-04-01 19:42 ` [PATCH] Kyle Moffett
2007-04-01 19:47 ` [PATCH] Jan Engelhardt
2007-04-01 20:07 ` [PATCH] Kyle Moffett
2007-04-01 19:50 ` [PATCH] Add a CONFIG_I_KNOW_WHAT_THE_HELL_I_AM_DOING variable Kyle Moffett
2007-04-01 23:03 ` [PATCH] Andi Kleen
2007-04-01 20:22 ` [PATCH 07/16] kconfig-dynamic-frequency.diff Robert P. J. Day
2007-04-01 18:15 ` [PATCH 08/16] console-printk-level.diff Jan Engelhardt
2007-04-01 19:07 ` Randy Dunlap
2007-04-01 18:15 ` [PATCH 09/16] zlib-decompression-status.diff Jan Engelhardt
2007-04-02 17:48 ` Jörn Engel
2007-04-02 18:50 ` Jan Engelhardt
2007-04-01 18:15 ` [PATCH 10/16] show-partitions-on-mount-error.diff Jan Engelhardt
2007-04-02 5:47 ` Andrew Morton
2007-04-02 5:48 ` Andrew Morton
2007-04-02 7:01 ` [PATCH 10/16] show partitions on mount error Jan Engelhardt
2007-04-02 18:59 ` [PATCH 10/16] show-partitions-on-mount-error.diff Pavel Machek
2007-04-04 0:42 ` Jan Engelhardt
2007-04-01 18:16 ` [PATCH 11/16] samba-eintr-fix.diff Jan Engelhardt
2007-04-01 19:09 ` Dave Jones
2007-04-01 19:28 ` Jan Engelhardt
2007-04-01 19:42 ` Dave Jones
2007-04-02 5:53 ` Andrew Morton
2007-04-01 18:16 ` [PATCH 12/16] cifs-use-mutex.diff Jan Engelhardt
2007-04-02 5:36 ` Roland Dreier
2007-04-01 18:17 ` [PATCH 13/16] show-pipesize-in-stat.diff Jan Engelhardt
2007-04-02 5:58 ` Andrew Morton
2007-04-02 6:48 ` Jan Engelhardt
2007-04-02 10:41 ` Eric Dumazet
2007-04-04 0:48 ` Jan Engelhardt
2007-04-04 5:03 ` Eric Dumazet
2007-04-17 8:05 ` Jan Engelhardt
2007-04-01 18:17 ` [PATCH 14/16] kconfig-allow-override.diff Jan Engelhardt
2007-04-01 18:44 ` Sam Ravnborg
2007-04-01 19:09 ` Randy Dunlap
2007-04-01 18:18 ` [PATCH 15/16] use-regular-eth-suffix.diff Jan Engelhardt
2007-04-01 18:42 ` Kyle Moffett
2007-04-02 1:40 ` Jouni Malinen [this message]
2007-04-01 18:18 ` [PATCH 16/16] warn-on-kthread-name-truncation.diff Jan Engelhardt
2007-04-02 6:00 ` Andrew Morton
2007-04-02 6:51 ` Jan Engelhardt
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=20070402014003.GS16197@jm.kir.nu \
--to=j@w1.fi \
--cc=akpm@osdl.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pe1rxq@amsat.org \
/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