From: James <bjlockie@lockie.ca>
To: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Unspecified failure
Date: Thu, 27 Jan 2011 12:38:22 -0500 [thread overview]
Message-ID: <4D41AD8E.5040500@lockie.ca> (raw)
How can I find out what the "Unspecified failure" is?
$ sudo iw --debug dev wlan1 connect -w "test"
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 164
.nlmsg_type = 18 <0x12>
.nlmsg_flags = 0 <>
.nlmsg_seq = 0
.nlmsg_pid = 0
[PAYLOAD] 148 octets
21 01 00 00 08 00 01 00 00 00 00 00 08 00 03 00 03 00 !.................
00 00 0c 00 2d 00 08 00 00 00 74 65 73 74 74 00 2c 00 ....-.....testt.,.
08 00 00 00 6c 09 00 00 08 00 01 00 71 09 00 00 08 00 ....l.......q.....
02 00 76 09 00 00 08 00 03 00 7b 09 00 00 08 00 04 00 ..v.......{.......
80 09 00 00 08 00 05 00 85 09 00 00 08 00 06 00 8a 09 ..................
00 00 08 00 07 00 8f 09 00 00 08 00 08 00 94 09 00 00 ..................
08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 00 00 08 00 ..................
0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 08 00 0d 00 ..................
b4 09 00 00 ....
--------------------------- END NETLINK MESSAGE
---------------------------
-- Error: Invalid message: type=0x12 length=164 flags=<> sequence-nr=0 pid=0
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 36
.nlmsg_type = 2 <ERROR>
.nlmsg_flags = 0 <>
.nlmsg_seq = 1296149664
.nlmsg_pid = 2927
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.nlmsg_type = 18 <0x12>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1296149664
.nlmsg_pid = 2927
--------------------------- END NETLINK MESSAGE
---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 164
.nlmsg_type = 18 <0x12>
.nlmsg_flags = 0 <>
.nlmsg_seq = 0
.nlmsg_pid = 0
[PAYLOAD] 148 octets
22 01 00 00 08 00 01 00 00 00 00 00 08 00 03 00 03 00 ".................
00 00 0c 00 2d 00 08 00 00 00 74 65 73 74 74 00 2c 00 ....-.....testt.,.
08 00 00 00 6c 09 00 00 08 00 01 00 71 09 00 00 08 00 ....l.......q.....
02 00 76 09 00 00 08 00 03 00 7b 09 00 00 08 00 04 00 ..v.......{.......
80 09 00 00 08 00 05 00 85 09 00 00 08 00 06 00 8a 09 ..................
00 00 08 00 07 00 8f 09 00 00 08 00 08 00 94 09 00 00 ..................
08 00 09 00 99 09 00 00 08 00 0a 00 9e 09 00 00 08 00 ..................
0b 00 a3 09 00 00 08 00 0c 00 a8 09 00 00 08 00 0d 00 ..................
b4 09 00 00 ....
--------------------------- END NETLINK MESSAGE
---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 52
.nlmsg_type = 18 <0x12>
.nlmsg_flags = 0 <>
.nlmsg_seq = 0
.nlmsg_pid = 0
[PAYLOAD] 36 octets
25 01 00 00 08 00 01 00 00 00 00 00 08 00 03 00 03 00 %.................
00 00 04 00 41 00 0a 00 06 00 00 18 3f b6 7d 69 00 00 ....A.......?.}i..
--------------------------- END NETLINK MESSAGE
---------------------------
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE
---------------------------
[HEADER] 16 octets
.nlmsg_len = 56
.nlmsg_type = 18 <0x12>
.nlmsg_flags = 0 <>
.nlmsg_seq = 0
.nlmsg_pid = 0
[PAYLOAD] 40 octets
2e 01 00 00 08 00 01 00 00 00 00 00 08 00 03 00 03 00 ..................
00 00 0a 00 06 00 00 18 3f b6 7d 69 00 00 06 00 48 00 ........?.}i....H.
01 00 00 00 ....
--------------------------- END NETLINK MESSAGE
---------------------------
wlan1 (phy #0): failed to connect to 00:18:3f:b6:7d:69, status: 1:
Unspecified failure
reply other threads:[~2011-01-27 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D41AD8E.5040500@lockie.ca \
--to=bjlockie@lockie.ca \
--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 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).