Hi Monthadar and others,
I'm starting to tackle this again.
-a
On 29 July 2013 06:11, Adrian Chadd wrote:
> So what's the specific difference between normal station and meshSTA?
>
>
>
> -adrian
>
> On 29 July 2013 03:24, Monthadar Al Jaberi wrote:
>> On Mon, Jul 29, 2013 at 5:32 AM, Adrian
So what's the specific difference between normal station and meshSTA?
-adrian
On 29 July 2013 03:24, Monthadar Al Jaberi wrote:
> On Mon, Jul 29, 2013 at 5:32 AM, Adrian Chadd wrote:
>> Hi,
>>
>> * I think we can get away with one queue per mesh STA neighbor for
>> now. Which is effectively w
On Mon, Jul 29, 2013 at 5:32 AM, Adrian Chadd wrote:
> Hi,
>
> * I think we can get away with one queue per mesh STA neighbor for
> now. Which is effectively what we have in ath(4) and we will have in
> net80211 soon
Yupp, the 80211 queue per meshSTA neighbour part is important if we
want to queu
Hi,
* I think we can get away with one queue per mesh STA neighbor for
now. Which is effectively what we have in ath(4) and we will have in
net80211 soon
* THanks for the clarification for mesh sequence number. So we:
+ Increment it if we're generating a frame into the mesh network;
+ Keep it
On Tue, Jul 9, 2013 at 1:33 AM, Adrian Chadd wrote:
> On 8 July 2013 16:00, Monthadar Al Jaberi wrote:
>
>>>
>>> * What's supposed to happen to the mesh sequence number?
>>
>> Mesh sequence number should be decreased with 1.
>
> Decreased or increased by one?
>
> I can see the mesh TTL being decr
On 8 July 2013 16:00, Monthadar Al Jaberi wrote:
>>
>> * What's supposed to happen to the mesh sequence number?
>
> Mesh sequence number should be decreased with 1.
Decreased or increased by one?
I can see the mesh TTL being decremented by one.
>> * What's supposed to happen to the QoS header
Hi,
On Sun, Jul 7, 2013 at 10:58 PM, Adrian Chadd wrote:
> Hi monthadar (and others),
>
> I'm tidying up the 802.11s TX path in preparation to support 802.11n,
> encryption, power-save handling, aggregation/fast-frames and other
> such loveliness.
>
> In order to do this, the 802.11s TX path need
Hi monthadar (and others),
I'm tidying up the 802.11s TX path in preparation to support 802.11n,
encryption, power-save handling, aggregation/fast-frames and other
such loveliness.
In order to do this, the 802.11s TX path needs to use the existing VAP
methods to encapsulate and queue frames rathe
