On Tue, Jun 25, 2013 at 8:25 AM, Conor O'Gorman <i...@conorogorman.net> wrote:
> On Tue, 2013-06-25 at 00:20 -0400, jonsm...@gmail.com wrote:
>> Can this be made to work on Ralink? When I have the adhoc0 interface
>> up bringing up ap0 says interface busy.....
>>
>
> Ralink is not good for supporting this type of setup. I had tried AP and
> client mode, and after some hacking it sort-of worked.
>
> From my notes:
> "ifconfig: SIOCSIFFLAGS: Device or resource busy". Looking at the output
> of 'iw list' the "valid interface combinations" only listed AP and mesh
> mode, not Station/Managed mode. On further investigation, none of the
> Ralink chips are fully supporting AP+Sta mode. After forcing the driver
> to report that it can support the combination, I was able to configure
> both interfaces as desired. The hack gives the following combination
> output:
> Pre:
> valid interface combinations:
> * #{ AP, mesh point } <= 8,
> total <= 8, #channels <= 1
> Post:
> valid interface combinations:
> * #{ managed, AP, mesh point } <= 8,
> total <= 8, #channels <= 1
>
> You may wish to force add 'adhoc' (P2P?) mode, and see how far it gets
> you. This was on an RT28xx USB device, so you may have more success on
> others.
>
> Hack (for test) looked like:
>
> --- a/drivers/net/wireless/rt2x00/rt2x00dev.c
> +++ b/drivers/net/wireless/rt2x00/rt2x00dev.c
> @@ -1264,7 +1264,7 @@ static inline void rt2x00lib_set_if_comb
> */
> if_limit = &rt2x00dev->if_limits_ap;
> if_limit->max = rt2x00dev->ops->max_ap_intf;
> - if_limit->types = BIT(NL80211_IFTYPE_AP);
> + if_limit->types = BIT(NL80211_IFTYPE_STATION) |
> BIT(NL80211_IFTYPE_AP);
> #ifdef CONFIG_MAC80211_MESH
> if_limit->types |= BIT(NL80211_IFTYPE_MESH_POINT);
> #endif
This fix has been committed to mainline...
I'm looking at getting simultaneous adhoc going.
commit 4a5fc6d7074de72dd836fbb9c5cd79f9a491871c
Author: Chun-Yeow Yeoh <yeohchuny...@gmail.com>
Date: Fri Jan 25 12:47:50 2013 +0800
rt2x00: allow AP and mesh mode to operate simultaneously
Allow AP and Mesh mode to operate concurrently using
single radio. Verify this using fonera 2.0n featuring
RT3052 chipset and also TP-LINK TL-WN727N featuring
RT5370 chipset.
Signed-off-by: Chun-Yeow Yeoh <yeohchuny...@gmail.com>
Acked-by: Helmut Schaa <helmut.sc...@googlemal.com>
Acked-by: Gertjan van Wingerde <gwinge...@gmail.com>
Signed-off-by: John W. Linville <linvi...@tuxdriver.com>
diff --git a/drivers/net/wireless/rt2x00/rt2x00dev.c
b/drivers/net/wireless/rt2x00/rt2x00dev.c
index 92a0aa5..1031db6 100644
--- a/drivers/net/wireless/rt2x00/rt2x00dev.c
+++ b/drivers/net/wireless/rt2x00/rt2x00dev.c
@@ -1236,7 +1236,8 @@ static inline void
rt2x00lib_set_if_combinations(struct rt2x00_dev *rt2x00dev)
*/
if_limit = &rt2x00dev->if_limits_ap;
if_limit->max = rt2x00dev->ops->max_ap_intf;
- if_limit->types = BIT(NL80211_IFTYPE_AP);
+ if_limit->types = BIT(NL80211_IFTYPE_AP) |
+ BIT(NL80211_IFTYPE_MESH_POINT);
/*
* Build up AP interface combinations structure.
>
> A nice Atheros (AR9330) shows good support for combinations:
>
> valid interface combinations:
> * #{ managed, WDS, P2P-client } <= 2048, #{ IBSS, AP, mesh
> point, P2P-GO } <= 8,
> total <= 2048, #channels <= 1
>
>
> Conor
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--
Jon Smirl
jonsm...@gmail.com
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
