From mboxrd@z Thu Jan 1 00:00:00 1970 From: Date: Fri, 23 Jul 2010 10:05:26 -0000 Subject: No subject Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org mesh point. We have not yet figured out why the mesh interface is removed a= nd reset to an interface of type NL80211_IFTYPE_STATION. Regards Abhijeet -----Original Message----- From: Luis R. Rodriguez [mailto:mcgrof at gmail.com] Sent: Wednesday, July 28, 2010 9:23 PM To: Abhijeet Chandran Cc: ath9k-devel at lists.ath9k.org Subject: Re: [ath9k-devel] ath9k mesh point not emitting beacons On Wed, Jul 28, 2010 at 7:19 AM, Abhijeet Chandran wrote: > Hi > We have a problem that we have configured a mesh point for the first > time and it does not seem to start emitting beacons as soon as it comes= up. > The card we are using is ath 9220 > We brought mesh point up , ex: > # iw phy phy0 interface add mesh type mp mesh_id mymesh # ifconfig > mesh up > > Through tracing in the kernel module mac80211 it appears that a > callback function ieee80211_open is called with type mesh point as > soon as the above commands are executed. > However it is immediately followed by the callback function > ieee80211_stop (usually called when the mesh point is brought down) , > following which the meshpoint related sdata is flushed . > Another question that we have is that do we need to enable scanning > for the mesh point to emit beacons/probes? > > We have used the simulator mac80211_hwsim before in which beacons are > emitted as soon as the mesh point comes up.In the simulator don't need > to start scanning on the mesh point. > We'd really appreciate if somone can help us out here. Known issue no one has yet looked into: https://bugzilla.kernel.org/show_bug.cgi?id=3D14187 It should start beaconing if you issue a scan. Luis "DISCLAIMER: This message is proprietary to Aricent and is intended solely = for the use of the individual to whom it is addressed. It may contain privi= leged or confidential information and should not be circulated or used for = any purpose other than for what it is intended. If you have received this m= essage in error, please notify the originator immediately. If you are not t= he intended recipient, you are notified that you are strictly prohibited fr= om using, copying, altering, or disclosing the contents of this message. Ar= icent accepts no responsibility for loss or damage arising from the use of = the information transmitted by this email including damage from virus."