netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jouni Malinen" <jkm@devicescape.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	mabbas <mabbas@linux.intel.com>,
	netdev@vger.kernel.org, jbenc@suse.cz
Subject: Re: [PATCH 4/7] d80211: add support for SIOCSIWNICKN SIOCGIWNICKN
Date: Tue, 29 Aug 2006 10:45:31 -0700	[thread overview]
Message-ID: <20060829174531.GH1701@instant802.com> (raw)
In-Reply-To: <20060829114915.GB29669@tuxdriver.com>

On Tue, Aug 29, 2006 at 07:49:22AM -0400, John W. Linville wrote:
> On Tue, Aug 29, 2006 at 09:49:17AM +0200, Johannes Berg wrote:
> > I intend to kill the nick command with nl80211 since it seems to be
> > useless. Any objections?
> 
> I can't defend it myself, but I have heard of people using it.
> I think some of the distro's init scripts might set it as well?
> 
> Can anyone defend the practice of setting a nickname for a wireless
> device?

I think that this was added either based on a non-802.11 protocol or
based on a specific hardware/firmware design that had possibility of
configuring a name for the client (to be exchanged with some proprietary
network management protocol as the device name).

After that, this ioctl seems to be just used for binding some arbitrary
data to an interface to help scripts etc. In other words, I don't see
any real use for this from the view point of IEEE 802.11 networks and it
is confusing at best. This may be useful for some setup scripts, but I
would rather hope they would use something else instead.

The only reason for adding nick command would be to maintain backwards
compatibility with some scripts. I do not use any distro configuration
mechanisms for setting up wireless, so I do not know what is currently
being used. I would not add these ioctls into d80211 unless someone can
point out an existing (and widely used) mechanism that depends on these
ioctls being available.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2006-08-29 17:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 20:50 [PATCH 4/7] d80211: add support for SIOCSIWNICKN SIOCGIWNICKN mabbas
2006-08-29  7:49 ` Johannes Berg
2006-08-29 11:49   ` John W. Linville
2006-08-29 17:45     ` Jouni Malinen [this message]
2006-08-29 22:15       ` Ulrich Kunitz
2006-08-29 22:26         ` Michael Wu
2006-08-30 13:36         ` Dan Williams
2006-09-21 16:52 ` Jiri Benc

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=20060829174531.GH1701@instant802.com \
    --to=jkm@devicescape.com \
    --cc=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linville@tuxdriver.com \
    --cc=mabbas@linux.intel.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).