From: Luca Coelho <luca@coelho.fi>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Kalle Valo <kvalo@adurom.com>,
Johannes Berg <johannes@sipsolutions.net>,
Calvin Owens <jcalvinowens@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ieee80211: Print human-readable disassoc/deauth reason codes
Date: Sat, 08 Feb 2014 00:25:34 +0200 [thread overview]
Message-ID: <1391811934.18534.54.camel@porter.coelho.fi> (raw)
In-Reply-To: <52F4FFD5.5070808@lwfinger.net>
On Fri, 2014-02-07 at 09:46 -0600, Larry Finger wrote:
> On 02/07/2014 06:53 AM, Kalle Valo wrote:
> > Johannes Berg <johannes@sipsolutions.net> writes:
> >
> >> On Wed, 2014-02-05 at 19:44 -0600, Calvin Owens wrote:
> >>> Create a function to return a descriptive string for each reason code,
> >>> and print that instead of the numeric value in the kernel log. These
> >>> codes are easily found on popular search engines, but one is generally
> >>> not able to access the internet when dealing with wireless connectivity
> >>> issues.
> >>
> >> I believe both iw and wpa_supplicant already have the reason code
> >> printout, and if you're diagnosing connectivity issues then you're
> >> probably using those anyway (e.g. iw event -t), so I don't really see
> >> much point in adding this to the kernel?
> >
> > FWIW I find this useful. When I have connection problems I rarely look
> > at wpasupplicant, mostly I'm so lazy that I just check from the kernel
> > log what's happening. Just my 0.02 EUR.
>
> I would also find it useful. I assist with wireless problems on the openSUSE
> Forum, and there we are lucky if we get dmesg output. When we do and it contains
> a deauthentication reason, I always need to bring up a web page to interpret the
> output. With this change, one step could be skipped.
But is it worth putting this parsing in the *kernel*? I mean, if anyone
is interested enough in the problem, a simple google query is not that
hard, right?
If this happens to you "on-the-fly" and all you want is your connection
to work, you won't start debugging right away. You'll (maybe) save the
kernel logs, try to reconnect and debug later, at home.
If you think you *can* fix the problem on-the-fly, but you can't google
because the connection doesn't work, you certainly have either the IEEE
802.11 specs or the kernel sources somewhere in your device. :)
--
Luca.
next prev parent reply other threads:[~2014-02-07 22:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 1:44 Calvin Owens
2014-02-06 4:44 ` Joe Perches
2014-02-10 11:09 ` Johannes Berg
2014-02-10 16:39 ` Joe Perches
2014-02-11 1:25 ` [PATCH v2] " Calvin Owens
2014-02-11 1:39 ` Joe Perches
2014-02-11 16:37 ` [PATCH v3] " Calvin Owens
2014-02-11 16:48 ` Antonio Quartulli
2014-02-11 17:59 ` Calvin Owens
2014-02-11 18:19 ` Johannes Berg
2014-02-11 17:13 ` Joe Perches
2014-02-11 17:52 ` Calvin Owens
2014-02-11 18:36 ` [PATCH v4] " Calvin Owens
2014-02-12 10:46 ` Johannes Berg
2014-02-06 8:37 ` [PATCH] " Johannes Berg
2014-02-07 12:53 ` Kalle Valo
2014-02-07 15:46 ` Larry Finger
2014-02-07 22:25 ` Luca Coelho [this message]
2014-02-08 6:38 ` Kalle Valo
2014-02-07 20:50 ` Calvin Owens
2014-02-10 8:50 ` 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=1391811934.18534.54.camel@porter.coelho.fi \
--to=luca@coelho.fi \
--cc=Larry.Finger@lwfinger.net \
--cc=davem@davemloft.net \
--cc=jcalvinowens@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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
all inboxes | Powered by JetHome®