[ath9k-devel] [PATCH] ath9k: Support RSN Mesh

[gtolon at inti.gob.ar <gtolon@inti.gob.ar>]

Hi Chun-Yeow

I don't know if this is usefull for you, but we are using ad hoc with 
batman-adv, and we had some problems when the nodes didn't choose good 
routes for high throughputs for relatively long distances. Asking to the 
batman-adv list they explained us that the algorithm to choose the 
routes is based on low rate broadcasts, so the nodes could choose routes 
that with high rates become bad. They suggested us to increase the 
multicast rates, so that the nodes could "realize" if a route were not 
good for high throughputs, and it worked better, the nodes chose routes 
with more hops for long distances getting a better throughput than using 
less hops with larger distances.

By the way, why with nohwcrypt=1 the throughput get worse?

Regards

Gabriel

El 02/12/2011 07:04 a.m., Yeoh Chun-Yeow escribi?:
> Hi, Shafi
>
> I am active in open80211s mailing list. Thomas from cozybit is helping 
> me quite a lot. Just wonder any peoples here working on adhoc multihop 
> on ath9k facing the same problem when doing throughput test for 
> multihop environment.
>
> Regards,
> Chun-Yeow
>
> On Fri, Dec 2, 2011 at 6:01 PM, Mohammed Shafi 
> <shafi.wireless at gmail.com <mailto:shafi.wireless@gmail.com>> wrote:
>
>     Hi  Chun-Yeow ,
>
>     sorry i have no idea and have not tested mesh. please also send a mail
>     to linux wireless mailing list, where you may get some help from mesh
>     developers from cozy bit.
>
>     On Fri, Dec 2, 2011 at 3:21 PM, Yeoh Chun-Yeow
>     <yeohchunyeow at gmail.com <mailto:yeohchunyeow@gmail.com>> wrote:
>     > Hi, Shafi
>     >
>     > I am using AR9280 and AR9160. Let me explain the situation:
>     >
>     > Actually, we need to use per-STA RX GTK for secured mesh. Thus,
>     we use
>     > software crypto for our multicast/broadcast frame. Without this
>     patch, we
>     > need to load the ath9k with nohwcrypt=1. Thus, we suffer the
>     throughput
>     > performance of our mesh nodes on unicast frame (no software
>     crypto as well).
>     > After applying this patch, we are able to get HT throughput for
>     single hop
>     > communication in mesh setup (802.11s) by enabling HW crypto for
>     unicast.
>     >
>     > However, we are still having throughput performance on multihop
>     > communication. Do you have any idea?
>     >
>     > Regards,
>     > Chun-Yeow
>     >
>     > On Fri, Dec 2, 2011 at 5:38 PM, Mohammed Shafi
>     <shafi.wireless at gmail.com <mailto:shafi.wireless@gmail.com>>
>     > wrote:
>     >>
>     >> Hi Chun-Yeow Yeoh,
>     >>
>     >> ath9k.ko with nohwcrypt=1 disables hardware encryption and your
>     patch
>     >> also does the same for mesh mode. i need to look into the code
>     what it
>     >> does, as i don't know about the details and also i have not tested
>     >> mesh.
>     >> also what card you are using? please make sure you  are using the
>     >> latest ath9k build.
>     >> please send patches to linux wireless mailing list
>     >> http://linuxwireless.org/en/developers/Documentation/git-guide
>     >> thank you
>     >>
>     >> On Fri, Dec 2, 2011 at 2:53 PM, Yeoh Chun-Yeow
>     <yeohchunyeow at gmail.com <mailto:yeohchunyeow@gmail.com>>
>     >> wrote:
>     >> > Hi, Shafi
>     >> >
>     >> > Appreciate if you can comment on this. Previous, for mesh
>     node setup, we
>     >> > need to load the ath9k.ko with nohwcrypt=1. After applying
>     this patch,
>     >> > we
>     >> > can simply load the ath9k.ko without nohwcrypt=1 and able to
>     ensure the
>     >> > mesh
>     >> > node communicate. Besides, we can achieve HT throughput for
>     single hop
>     >> > mesh
>     >> > setup, but still problematic on multi-hop mesh setup.
>     >> >
>     >> > Thanks
>     >> >
>     >> > Regards,
>     >> > Chun-Yeow
>     >> >
>     >> >
>     >> > On Fri, Dec 2, 2011 at 5:18 PM, Mohammed Shafi
>     >> > <shafi.wireless at gmail.com <mailto:shafi.wireless@gmail.com>>
>     >> > wrote:
>     >> >>
>     >> >> Hi Chun-Yeow Yeoh,
>     >> >>
>     >> >> On Fri, Dec 2, 2011 at 2:21 PM, Yeoh Chun-Yeow
>     <yeohchunyeow at gmail.com <mailto:yeohchunyeow@gmail.com>>
>     >> >> wrote:
>     >> >> > From: Chun-Yeow Yeoh <yeohchunyeow@gmail.com
>     <mailto:yeohchunyeow@gmail.com>>
>     >> >> > Date: Fri, 18 Nov 2011 10:04:38 +0800
>     >> >> > Subject: [PATCH] ath9k: Support RSN Mesh
>     >> >> >
>     >> >> > Enable support of HW crypt for Mesh to achieve high
>     throughput.
>     >> >>
>     >> >> i think you are doing the other way around in your patch.
>     >> >>
>     >> >> >
>     >> >> > Signed-off-by: Chun-Yeow Yeoh <yeohchunyeow@gmail.com
>     <mailto:yeohchunyeow@gmail.com>>
>     >> >> > ---
>     >> >> >  drivers/net/wireless/ath/ath9k/main.c |    3 ++-
>     >> >> >  1 files changed, 2 insertions(+), 1 deletions(-)
>     >> >> >
>     >> >> > diff --git a/drivers/net/wireless/ath/ath9k/main.c
>     >> >> > b/drivers/net/wireless/ath/ath9k/main.c
>     >> >> > index 93fbe6f..1536515 100644
>     >> >> > --- a/drivers/net/wireless/ath/ath9k/main.c
>     >> >> > +++ b/drivers/net/wireless/ath/ath9k/main.c
>     >> >> > @@ -1912,7 +1912,8 @@ static int ath9k_set_key(struct
>     ieee80211_hw
>     >> >> > *hw,
>     >> >> >
>     >> >> >         if (ath9k_modparam_nohwcrypt)
>     >> >> >                 return -ENOSPC;
>     >> >> >
>     >> >> > -       if (vif->type == NL80211_IFTYPE_ADHOC &&
>     >> >> > +       if ((vif->type == NL80211_IFTYPE_ADHOC ||
>     >> >> > +            vif->type == NL80211_IFTYPE_MESH_POINT) &&
>     >> >> >             (key->cipher == WLAN_CIPHER_SUITE_TKIP ||
>     >> >> >              key->cipher == WLAN_CIPHER_SUITE_CCMP) &&
>     >> >> >             !(key->flags & IEEE80211_KEY_FLAG_PAIRWISE)) {
>     >> >> > --
>     >> >> > 1.7.0.4
>     >> >> >
>     >> >> >
>     >> >> >
>     >> >> > _______________________________________________
>     >> >> > ath9k-devel mailing list
>     >> >> > ath9k-devel at lists.ath9k.org
>     <mailto:ath9k-devel@lists.ath9k.org>
>     >> >> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>     >> >> >
>     >> >>
>     >> >>
>     >> >>
>     >> >> --
>     >> >> shafi
>     >> >
>     >> >
>     >>
>     >>
>     >>
>     >> --
>     >> shafi
>     >
>     >
>
>
>
>     --
>     shafi
>
>
>
> _______________________________________________
> ath9k-devel mailing list
> ath9k-devel at lists.ath9k.org
> https://lists.ath9k.org/mailman/listinfo/ath9k-devel