> From: devel-requ...@lists.open80211s.org > Subject: Devel Digest, Vol 45, Issue 7 > To: devel@lists.open80211s.org > Date: Sat, 11 Jun 2011 12:00:02 -0400 > > Send Devel mailing list submissions to > devel@lists.open80211s.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://open80211s.com/mailman/listinfo/devel > or, via email, send a message with subject or body 'help' to > devel-requ...@lists.open80211s.org > > You can reach the person managing the list at > devel-ow...@lists.open80211s.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Devel digest..." > > > Today's Topics: > > 1. Re: Problem on Release0.4.0 (Javier Cardona) > 2. Re: Mesh Access Point (MAP) Support in open80211s (Javier Cardona) > 3. Re: [ath9k-devel] [RFC] ath9k_htc: Add support for > NL80211_IFTYPE_MESH_POINT interfaces (Javier Cardona) > 4. Re: Mesh Access Point (MAP) Support in open80211s (Yeoh Chun Yeow) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 10 Jun 2011 11:14:15 -0700 > From: Javier Cardona <jav...@cozybit.com> > Subject: Re: Problem on Release0.4.0 > To: devel@lists.open80211s.org > Message-ID: <BANLkTi=9mbgwdjlfodl1qjxg6ngndc5...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi V-Shy, > > I don't have all the answers to your questions, but I'll try to answer > the ones I know: > > On Fri, Jun 10, 2011 at 2:33 AM, V-SHY HO <vshy...@hotmail.com> wrote: > > Hi Javier, > > > > May I ask > > > > 1) How can we determine the support for multiple GTKs? > > ?? a) only from the wireless NIC datasheet? > > ?? b) Do ath9k driver support this? > > You probably should ask in the ath9k mailing list. This is not mesh > specific but rather a driver/hardware feature. > > > 2) There have two type of API, non-NAPI and NAPI (New API). > > ?? a)may I know how I determine my Dlink DWA 547 (Atheros AR9280) using > > which API? > > Adding net_ratelimit() guarded printk's to the data path? > > > ?? b)for open80211s, it always make use of netif_rx function (non-API) to > > notify kernel about a new frame? > > open80211s is part of mac80211 and uses the same functions to pass > traffic to the upper layers via netif_receive_skb(). See > ieee80211_deliver_skb() in mac80211/rx.c > > > 3) For non-NAPI device, the receive frame is placed at > > softnet_data->input_pkt_queue > > ? a)is it possible to observe frame content which is placed at the queue? > > ????? i)via /proc ? > > To examine frames you probably want to use a monitor interface: > http://linuxwireless.org/en/users/Documentation/iw/vif/#Monitor > > > 4) To prevent ath9k drop the encrypted broadcast frame > > ?? a)the ath9k driver need to have new patch? > > On our hardware (TP-Link TL-WN821N ) we needed this patch *and* load > the driver with nohwcrypt=1 (i.e. doing the encryption in software). > This is probably a bug in mac80211 or the driver given because why > would hardware capabilities affect encryption if we tell the driver to > do it in software? But I did not want to wait for this to be resolved > before sharing our changes. This way other people can start testing > on ath9k_htc hardware. > > > ?? b)do linux provide the way to observe the content of the frame after > > ath9k process and waiting passing to mac80211? > > Yes, the monitor interface should let you do that. > > Cheers, > > Javier > > > > thanks > > > > V-SHY HO > > > > > > > >> Date: Tue, 7 Jun 2011 11:43:07 -0700 > >> From: Javier Cardona <jav...@cozybit.com> > >> Subject: Re: Problem on Release0.4.0 > > > >> Thank you for the captures. This is the same problem we've observed > >> on our ath9k cards and seems to be related to key installation. For > >> secured mesh to work the driver/device need to support multiple Group > >> Temporal Keys (GTKs) as a different key will be required to decrypt > >> broadcast traffic from each peer. The authsae daemon does exchange > >> gtk's with each authenticated peer and will install the keys > >> successfully. You've seen that with mac80211_hwsim, and you can > >> confirm that for your driver by inspecting the keys via debugfs. > >> But the ath9k driver seems to nuke the encrypted broadcast frame > >> before passing it to mac80211 for decryption. This is why there is no > >> response to those broadcast frames (which I assume are ARP requests to > >> resolve the MAC address of the peer) > >> > >> Thanks, > >> > >> Javier > >> > >> -- > >> Javier Cardona > >> cozybit Inc. > >> http://www.cozybit.com > > > > > > _______________________________________________ > > Devel mailing list > > Devel@lists.open80211s.org > > http://open80211s.com/mailman/listinfo/devel > > > > > > > > -- > Javier Cardona > cozybit Inc. > http://www.cozybit.com > > > ------------------------------ > > Message: 2 > Date: Fri, 10 Jun 2011 11:16:41 -0700 > From: Javier Cardona <jav...@cozybit.com> > Subject: Re: Mesh Access Point (MAP) Support in open80211s > To: devel@lists.open80211s.org > Cc: vshy...@hotmail.com > Message-ID: <BANLkTimNN=hfqprcz3wemy8gtgkkgw5...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Fri, Jun 3, 2011 at 1:08 AM, Yeoh Chun Yeow <yeohchuny...@gmail.com> wrote: > > I have read that the standard and it claims that we can do MAP. Yes, I am > > looking one single radio doing two things together. I am sure that there > > will be no problem using 2 radios by bridging AP and Mesh Node. > > I wish I was so sure :) > The challenge is to do dual beaconing on a single radio: mesh and AP > beacons are different and I don't know of a wireless card that > supports that. > > Javier > > > ------------------------------ > > Message: 3 > Date: Fri, 10 Jun 2011 11:22:23 -0700 > From: Javier Cardona <jav...@cozybit.com> > Subject: Re: [ath9k-devel] [RFC] ath9k_htc: Add support for > NL80211_IFTYPE_MESH_POINT interfaces > To: Pavel Roskin <pro...@gnu.org> > Cc: devel@lists.open80211s.org, ath9k-de...@lists.ath9k.org > Message-ID: <banlktik+xep-bdl4io91bfnnpczcja+...@mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Jun 7, 2011 at 9:43 AM, Pavel Roskin <pro...@gnu.org> wrote: > > Hello! > > > > You may want to copy to linux-wireless as well. ?You'll get more eyeballs > > looking at your code. > > Thanks for reviewing. > > > On 06/06/2011 08:55 PM, Javier Cardona wrote: > >> > >> More specifically, enable AP-style beaconing on mesh ifaces, honor > >> FIF_OTHER_BSS filter and change the hw capabilities to reflect mesh > >> support. > >> > >> Tested on two TP-Link TL-WN821N and with this patch we could establish > >> peer > >> links and ping. > > > > ... > >> > >> + ? ? ? case NL80211_IFTYPE_MESH_POINT: > >> + ? ? ? ? ? ? ? /* 802.11s defines a different beaconing method for mesh > >> points > >> + ? ? ? ? ? ? ? ?* that closely resembles AP-style beaconing. ?Until that > >> is > >> + ? ? ? ? ? ? ? ?* implemented, just use AP-style beaconing for mesh > >> points. */ > >> + ? ? ? ? ? ? ? /* Fall through */ > >> ? ? ? ?case NL80211_IFTYPE_AP: > >> ? ? ? ? ? ? ? ?ath9k_htc_beacon_config_ap(priv, cur_conf); > > > > Is it fundamentally impossible for AP and mesh VIFs to coexist? ?If it's > > possible, you may want to use NL80211_IFTYPE_AP even if there is a mesh VIF > > and use num_ap_vif and num_mbss_vif to code needed for AP and mesh > > respectively. > > It is not precluded by the standard, but requires that the hardware > can do dual-beaconing given that mesh and AP beacons are different: > different MAC address, frequency. etc. > > > Having distinct global opmodes would stand in the way if AP and mesh > > coexistence is to be implemented. > > Noted. It is definitively a doable and desired use case so we plan > the driver as if there will soon be hardware that can do it. (Or > maybe there is, do you know?) > > > By the way, we may want to use distinctive names for the common opmodes to > > avoid confusion with the VIF modes. > > > >> + ? ? ? if (priv->num_mbss_vif || > >> + ? ? ? ? ? (priv->nvifs&& ?vif->type == NL80211_IFTYPE_MESH_POINT)) { > >> + ? ? ? ? ? ? ? ath_err(common, "Mesh BSS coexistence with other modes is > >> not allowed\n"); > >> + ? ? ? ? ? ? ? mutex_unlock(&priv->mutex); > >> + ? ? ? ? ? ? ? return -ENOBUFS; > >> + ? ? ? } > > > > This code appears to allow only one mesh interface. ?Is that your intention? > > ?I think you just copied the code from Ad-Hoc without realizing what it > > does. > > Again I thought the hardware could not do dual beaconning. If it can, > then there is no need to limit the number of mesh vifs. > > >> + ? ? ? if (priv->rxfilter& ?FIF_OTHER_BSS) > >> + ? ? ? ? ? ? ? rfilt |= ATH9K_RX_FILTER_MCAST_BCAST_ALL; > > > > I think this could be a separate patch. ?It may have effect beyond mesh > > support. > > Noted. > > Thanks! > > Javier > > > -- > Javier Cardona > cozybit Inc. > http://www.cozybit.com > > > ------------------------------ > > Message: 4 > Date: Sat, 11 Jun 2011 14:24:29 +0800 > From: Yeoh Chun Yeow <yeohchuny...@gmail.com> > Subject: Re: Mesh Access Point (MAP) Support in open80211s > To: devel@lists.open80211s.org, Javier Cardona <jav...@cozybit.com> > Cc: vshy...@hotmail.com > Message-ID: <BANLkTinmGXG4e=dwqnitmwqryyyezb5...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, Javier > > Yes, I have tested two radios by bridging AP and Mesh node and it works. :) > > Is single radio with Mesh Node and AP functionalities not possible? Or we > need to do something to solve the dual beaconing issue? > > http://linuxwireless.org/en/developers/Documentation/ieee80211/802.11s > > Regards, > Chun Yeow > > On Sat, Jun 11, 2011 at 2:16 AM, Javier Cardona <jav...@cozybit.com> wrote: > > > On Fri, Jun 3, 2011 at 1:08 AM, Yeoh Chun Yeow <yeohchuny...@gmail.com> > > wrote: > > > I have read that the standard and it claims that we can do MAP. Yes, I am > > > looking one single radio doing two things together. I am sure that there > > > will be no problem using 2 radios by bridging AP and Mesh Node. > > > > I wish I was so sure :) > > The challenge is to do dual beaconing on a single radio: mesh and AP > > beacons are different and I don't know of a wireless card that > > supports that. > > > > Javier > > _______________________________________________ > > Devel mailing list > > Devel@lists.open80211s.org > > http://open80211s.com/mailman/listinfo/devel > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://open80211s.com/pipermail/devel/attachments/20110611/7ed77a71/attachment-0001.html > > > ------------------------------ > > _______________________________________________ > Devel mailing list > Devel@lists.open80211s.org > http://open80211s.com/mailman/listinfo/devel > > > End of Devel Digest, Vol 45, Issue 7 > ************************************
_______________________________________________ Devel mailing list Devel@lists.open80211s.org http://open80211s.com/mailman/listinfo/devel
