All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Patch to allow specification of interface name prefix
Date: Tue, 27 Feb 2007 13:52:21 -0500	[thread overview]
Message-ID: <1172602341.3291.8.camel@dv> (raw)
In-Reply-To: <45E4769E.2040102@candelatech.com>

On Tue, 2007-02-27 at 10:21 -0800, Ben Greear wrote:

> Regardless of the name, it would be nice to have some quick way to
> determine
> if a network device is wireless or not.  This could be an IOCTL, something
> in /proc/ or similar.  Even if you name them to be wlanX by default, folks
> can rename them, so applications that care about the type of the network
> device can't key off of names reliably...

iwconfig can do it using ioctl.  Shell scripts can do it using
"wireless" directory in sysfs:

for i in /sys/class/net/*; do
  if test -d $i/wireless; then
    echo `basename $i`
  fi
done

-- 
Regards,
Pavel Roskin


  reply	other threads:[~2007-02-27 18:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  4:06 Patch to allow specification of interface name prefix Alex Davis
2007-02-25  4:30 ` Pavel Roskin
2007-02-25  4:39   ` Larry Finger
2007-02-26 23:02     ` Stephen Hemminger
2007-02-27  1:33       ` John W. Linville
2007-02-27 10:16       ` Jiri Benc
2007-02-27 17:41         ` Stephen Hemminger
2007-02-27 18:21           ` Ben Greear
2007-02-27 18:52             ` Pavel Roskin [this message]
2007-02-27 19:15               ` Johannes Berg
2007-02-27 18:55         ` Luis R. Rodriguez
2007-02-28  1:25           ` John W. Linville
2007-02-28  8:51             ` Johannes Berg
2007-02-28 16:44             ` Jouni Malinen
2007-02-28 16:50               ` Johannes Berg
2007-02-28 16:54                 ` Luis R. Rodriguez
2007-02-28 16:55                 ` Jouni Malinen
2007-02-28 18:35               ` John W. Linville
2007-02-28 19:21                 ` Jouni Malinen

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=1172602341.3291.8.camel@dv \
    --to=proski@gnu.org \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.