From: "Alina Friedrichsen" <x-alina@gmx.net>
To: Johannes Berg <johannes@sipsolutions.net>, linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: split IBSS/managed code
Date: Fri, 13 Feb 2009 21:36:41 +0100 [thread overview]
Message-ID: <20090213203641.199830@gmx.net> (raw)
In-Reply-To: <1234396421.16004.67.camel@johannes.local>
Hello,
this patch is broken.
* In IBSS beaconing doesn't work.
* If you create a new IBSS network it
scans for other networks to often
3 times a second.
[ 844.752425] wlan0: sta_find_ibss (active_ibss=3D0)
[ 844.752435] did not try to join ibss
[ 844.752449] wlan0: No active IBSS STAs - trying to scan for other IB=
SS networks with same SSID (merge)
[ 846.032344] wlan0: sta_find_ibss (active_ibss=3D0)
[ 846.032356] did not try to join ibss
[ 846.051622] wlan0: No active IBSS STAs - trying to scan for other IB=
SS networks with same SSID (merge)
[ 847.214000] wlan0: sta_find_ibss (active_ibss=3D0)
[ 847.214009] did not try to join ibss
[ 847.214025] wlan0: No active IBSS STAs - trying to scan for other IB=
SS networks with same SSID (merge)
* If you join an existent IBSS it does
the following strange things:
[ 5238.150840] wlan5: expiring inactive STA ffff8800bb800340
[ 5238.150847] phy0: Removed STA ffff8800bb800340
[ 5238.161306] phy0: Destroyed STA ffff8800bb800340
[ 5238.161316] wlan5: No active IBSS STAs - trying to scan for other IB=
SS networks with same SSID (merge)
[ 5238.223183] phy0: Adding new IBSS station ffff8800bb81a04a (dev=3Dwl=
an5)
[ 5238.223205] phy0: Allocated STA ffff8800bb800340
[ 5238.223213] phy0: Inserted STA ffff8800bb800340
[ 5238.855114] wlan5: sta_find_ibss (active_ibss=3D0)
[ 5238.855147] sta_find_ibss: selected ffff88009942f040 current ffff=
8800bc0219f0
[ 5238.855150] did not try to join ibss
[ 5238.867113] wlan5: expiring inactive STA ffff8800bb800340
[ 5238.867122] phy0: Removed STA ffff8800bb800340
[ 5238.880673] phy0: Destroyed STA ffff8800bb800340
[ 5238.880684] wlan5: No active IBSS STAs - trying to scan for other IB=
SS networks with same SSID (merge)
[ 5238.943194] phy0: Adding new IBSS station ffff8800bb83a04a (dev=3Dwl=
an5)
[ 5238.943218] phy0: Allocated STA ffff8800bb800340
[ 5238.943226] phy0: Inserted STA ffff8800bb800340
[ 5239.572256] wlan5: sta_find_ibss (active_ibss=3D0)
[ 5239.572282] sta_find_ibss: selected ffff880099539640 current ffff=
8800bc0219f0
[ 5239.572285] did not try to join ibss
Regards
Alina
--=20
Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=
en: http://www.gmx.net/de/go/multimessenger01
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-13 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 23:53 [PATCH] mac80211: split IBSS/managed code Johannes Berg
2009-02-13 20:36 ` Alina Friedrichsen [this message]
2009-02-13 21:19 ` Johannes Berg
2009-02-13 21:43 ` Alina Friedrichsen
2009-02-13 21:51 ` Johannes Berg
2009-02-15 11:44 ` [PATCH v2] " Johannes Berg
2009-02-16 18:24 ` Alina Friedrichsen
2009-02-16 18:25 ` Johannes Berg
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=20090213203641.199830@gmx.net \
--to=x-alina@gmx.net \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).