Bug 13752 - rt2x00: mesh interface does not beacon until a scan is issued
Summary: rt2x00: mesh interface does not beacon until a scan is issued
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 21:25 UTC by Andrey Yurovsky
Modified: 2010-06-16 19:04 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.30
Tree: Mainline
Regression: No


Attachments

Description Andrey Yurovsky 2009-07-09 21:25:20 UTC
The rt2x00 driver does not start beaconing when a Mesh Point interface is brought up.  It, however, does start beaconing after a scan is issued.  To reproduce this, create and bring up a MP interface, for example:

# iw phy phy0 interface add mesh0 type mp mesh_id testing
# ifconfig mesh0 up

...and confirm that there are no beacons from the device via a network sniffer.  Then issue a scan:

# iwlist mesh0 scan

...and confirm that after the scan, the device beacons (and Mesh Point operation is working).
Comment 1 Ivo van Doorn 2009-09-17 18:49:49 UTC
Does it help when instead of scanning you simply switch channel once?
Comment 2 Andrey Yurovsky 2009-09-20 18:43:45 UTC
Yes, that works.  In fact you can specify channel 1 (the default channel for new mesh point interfaces) to start beaconing:

# iw phy phy0 interface add mesh type mp mesh_id mymesh
# ifconfig mesh up
# iw dev mesh set channel 1

Does this help narrow down the issue?
Comment 3 John W. Linville 2010-03-05 18:31:36 UTC
Ivo, anything more to add here?  Is this a driver issue, or a stack issue?  (I haven't investigated...)
Comment 4 Ivo van Doorn 2010-03-05 19:14:50 UTC
It is a driver issue. The problem is the initial configuration which requires the channel to be configured.
The issue should have been fixed some time again though. I did some patches in this area some time ago, so at least the latest kernel should work correctly.
Comment 5 John W. Linville 2010-05-13 15:04:27 UTC
Are current kernels (i.e. 2.6.34-rc7 or later) working for you?
Comment 6 John W. Linville 2010-06-16 19:04:15 UTC
Closed due to lack of response...

Note You need to log in before you can comment on or make changes to this bug.