From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>
Subject: Re: cfg80211: questions regarding cfg80211_ibss_joined()
Date: Tue, 1 Dec 2009 14:17:34 +0100 [thread overview]
Message-ID: <200912011417.34706.holgerschurig@gmail.com> (raw)
In-Reply-To: <1259672064.32171.76.camel@johannes.local>
> Are you running into the WARN_ON(!bss)?
No, I didn't get a bug, warning nor any output.
In the mean-time I found that this was because I didn't provide
any IE (I just submitted NULL & 0 to cfg80211_inform_bss).
Now I make a fake-IE with just WLAN_EID_SSID, and now I get
some "iw event" output:
# iw event
wlan0 (phy #0): IBSS 02:2a:ea:f0:a5:ef joined
> > need to fake some beacon data. Correct? Which IEs should
> > I add?
>
> As close to what your firmware is generating as you can get ...
Okay, will fire up wireshark :-)
--
http://www.holgerschurig.de
prev parent reply other threads:[~2009-12-01 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 12:47 cfg80211: questions regarding cfg80211_ibss_joined() Holger Schurig
2009-12-01 12:54 ` Johannes Berg
2009-12-01 13:17 ` Holger Schurig [this message]
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=200912011417.34706.holgerschurig@gmail.com \
--to=holgerschurig@gmail.com \
--cc=johannes@sipsolutions.net \
--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).