From: Baldomero Coll <baldo.ath9k@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: support for IEEE80211N in IBSS
Date: Thu, 3 Feb 2011 10:59:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20110203T115745-317@post.gmane.org> (raw)
In-Reply-To: 201101191438.01161.alexander.simon@saxnet.de
I have sacesfully installed the IBSS HT support patches [1] [2], but something
wrong happends when the network is created. Any idea why this happens?
[1]
# iw --debug dev wlan0 ibss join "uwicoreHT" 2412 HT20
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 36
.nlmsg_type = 2 <ERROR>
.nlmsg_flags = 0 <>
.nlmsg_seq = 1296727732
.nlmsg_pid = 2350
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.nlmsg_type = 23 <0x17>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1296727732
.nlmsg_pid = 2350
--------------------------- END NETLINK MESSAGE ---------------------------
[2]
iw --debug dev wlan0 ibss join "uwicoreHT" 2412 HT40-
-- Debug: Received Message:
-------------------------- BEGIN NETLINK MESSAGE ---------------------------
[HEADER] 16 octets
.nlmsg_len = 36
.nlmsg_type = 2 <ERROR>
.nlmsg_flags = 0 <>
.nlmsg_seq = 1296727811
.nlmsg_pid = 2354
[ERRORMSG] 20 octets
.error = 0 "Success"
[ORIGINAL MESSAGE] 16 octets
.nlmsg_len = 16
.nlmsg_type = 23 <0x17>
.nlmsg_flags = 5 <REQUEST,ACK>
.nlmsg_seq = 1296727811
.nlmsg_pid = 2354
--------------------------- END NETLINK MESSAGE ---------------------------
[3]
As a result, the iwconfig shows the following:
wlan0 IEEE 802.11abgn ESSID:"uwicoreHT"
Mode:Ad-Hoc Frequency:2.412 GHz Cell: Not-Associated
Tx-Power=30 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
(After few seconds the ESSID disappear)
wlan0 IEEE 802.11abgn Mode:Ad-Hoc Frequency:2.412 GHz
Cell: Not-Associated Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
next prev parent reply other threads:[~2011-02-03 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 13:38 [RFC] mac80211: support for IEEE80211N in IBSS Alexander Simon
2011-01-19 14:35 ` Johannes Berg
2011-01-20 9:10 ` [RFC 1/4] " Alexander Simon
2011-01-20 9:24 ` Johannes Berg
2011-01-20 9:48 ` Alexander Simon
2011-01-20 9:54 ` Johannes Berg
2011-01-20 10:15 ` Alexander Simon
2011-01-20 10:20 ` Johannes Berg
2011-01-20 9:21 ` [RFC 2/4] " Alexander Simon
2011-01-20 9:26 ` [RFC 3/4] " Alexander Simon
2011-01-20 9:37 ` [RFC 4/4] " Alexander Simon
2011-01-20 9:49 ` Johannes Berg
2011-01-26 16:31 ` [RFC] " Baldomero Coll
2011-02-03 10:59 ` Baldomero Coll [this message]
2011-02-04 17:10 ` Baldomero Coll
2011-02-04 17:22 ` Brian Prodoehl
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=loom.20110203T115745-317@post.gmane.org \
--to=baldo.ath9k@gmail.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 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).