.
On Tue, Mar 23, 2010 at 1:03 PM, Rui Paulo wrote:
>
> On 13 Mar 2010, at 16:17, Alexander Egorenkov wrote:
>
> > I have finally patched net80211 on my system and added HT extended
> capabilities support.
> >
> > Here are the patches.
> >
> > I added a n
Thu, Mar 11, 2010 at 8:44 AM, Rui Paulo wrote:
>
> On 11 Mar 2010, at 16:32, Alexander Egorenkov wrote:
>
> There are already constants defined in iee80211.h.
>> E.g. IEEE80211_HTCAP_MCSFBACK_UNSOL.
>>
>> But the problem is that e.g. IEEE80211_HTCAP_MCSFBACK_UNSOL
So how soon can we expect A-MPDU support in radiotap header ?
On Sun, Feb 21, 2010 at 12:25 AM, Rui Paulo wrote:
> On 20 Feb 2010, at 22:11, Sam Leffler wrote:
>
> > Rui Paulo wrote:
> >> On 20 Feb 2010, at 21:51, Sam Leffler wrote:
> >>> Alexander Egorenkov w
IEEE80211_HTCAP_MCSFBACK_UNSOL and
all other extended capability constant which conflict with normal HT
capability constants.
Or do you have any other ideas ?
On Thu, Mar 11, 2010 at 7:59 AM, Rui Paulo wrote:
> On 7 Mar 2010, at 17:04, Alexander Egorenkov wrote:
>
> OK, here is an example.
>>
>&g
with HTC+ and RDR
capabilities.
On Sun, Mar 7, 2010 at 1:16 AM, Sam Leffler wrote:
> Alexander Egorenkov wrote:
>
>> Currently there is no possibility to set some HT capabilities in e.g. an
>> association request frame.
>> The function ieee80211_add_htcap_body in ieee802
The following reply was made to PR kern/144476; it has been noted by GNATS.
From: Alexander Egorenkov
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/144476: [ieee80211] Incorrect "SM power save mode" HT
capability constants
Date: Fri, 5 Mar 2010 12:3
Currently there is no possibility to set some HT capabilities in e.g. an
association request frame.
The function ieee80211_add_htcap_body in ieee80211_ht.c simply sets some HT
capabilities to zero.
For example, there is no way to set HT extended capabilities which i need
for my 802.11n device drive
The following reply was made to PR kern/144476; it has been noted by GNATS.
From: Alexander Egorenkov
To: bug-follo...@freebsd.org, egore...@gmail.com
Cc:
Subject: Re: kern/144476: [ieee80211] Incorrect "SM power save mode" HT
capability constants
Date: Thu, 4 Mar 2010 21:2
The following reply was made to PR kern/143627; it has been noted by GNATS.
From: Alexander Egorenkov
To: bug-follo...@freebsd.org, egore...@gmail.com
Cc:
Subject: Re: kern/143627: [ieee80211] [panic] A bug in ht_send_action_ba_addba
causes net80211 to send malformed ADDBA response
The following reply was made to PR kern/144323; it has been noted by GNATS.
From: Alexander Egorenkov
To: bug-follo...@freebsd.org, egore...@gmail.com
Cc:
Subject: Re: kern/144323: [ieee80211] A response management frame appears in
wireshark captures before the corresponding request
I had to
change AMRR anyway, because ieee80211_amrr.c doesn't support HT nodes.
On Tue, Feb 23, 2010 at 1:01 PM, Rui Paulo wrote:
> On 21 Feb 2010, at 10:35, Alexander Egorenkov wrote:
>
> > This MCS32 HT rate causes problems with AMRR. If the connection between a
> > clien
, Sam Leffler wrote:
> Alexander Egorenkov wrote:
>
>
>>
>> On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler > s...@errno.com>> wrote:
>>
>>The advertised rate set should be initially set according to the
>>capabilities of the device. There were
I have encountered a problem with a 802.11n router Belkin F5D8631au.
The beacon and association response frames sent by this router do not
contain
WME information element although 802.11n mode is enabled. These frames
contain
HT capability IE and HT info. Because WME IE is missing in association
re
/s for unidirectional streams
> (netperf -t UDP_STREAM). Note that once you get to these higher rates
> things like TCP window sizes become important and doing things like TSO in
> s/w can give noticeable speed boosts.
>
>Sam
>
> Alexander Egorenkov wrote:
>
>>
and it worked, lucky me :-)
Alex.
On Sun, Jan 31, 2010 at 8:20 PM, Sam Leffler wrote:
> Alexander Egorenkov wrote:
>
>> Why doesn't 802.11 stack assign sequence numbers to A-MPDU frames ?
>>
>
> Because if net80211 does the assignment it may be wrong. As the comm
> What exactly do you need? We should be able to extend radiotap.
>
1. Not only one RSSI but for every antenna (also in dBm)
2. HT greenfield/HT mixed indicator
4. Number of spatial streams (STBC)
3. A-MPDU support (MPDU density, A-MPDU reassembly)
The most important one is A-MPDU support, i thin
Is it possible to use PPI header instead of Radiotap header in net80211 ? If
yes, how ?
Radiotap header is not sufficient for 802.11n mode and PPI header supports
802.11n mode very good.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/ma
On Sat, Feb 6, 2010 at 10:52 PM, Sam Leffler wrote:
> The advertised rate set should be initially set according to the
> capabilities of the device. There were no devices > 2x2 when I wrote the
> code so MCS15 is the max. To support such devices you need to do more than
> just grow the rateset.
And is any API in planning that would make it possible to change the
advertised HT rate set by STA during run time and not at compile time ? E.g.
ieee80211_set_ht_rateset :-)
On Sat, Feb 6, 2010 at 3:44 PM, Rui Paulo wrote:
> On 6 Feb 2010, at 08:28, Alexander Egorenkov wrote:
>
Hi,
the HT rate set advertized by a STA is hardcoded in net80211
and the maximum MCS is 15, but my device also supports MCS32 (HT duplicate
mode).
Is there a possibility to change the HT rates set advertized by a STA
except changing
the code and recompiling net80211 stack ?
Thanks.
Alex.
__
No, ralink.
On Sun, Jan 31, 2010 at 3:12 PM, Rui Paulo wrote:
>
> On 27 Jan 2010, at 19:04, Alexander Egorenkov wrote:
>
> > Hi,
> >
> > i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
>
> Just to make sure we don't step on
://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/io/net80211/net80211_output.c
Line: 211
Alex.
On Sun, Jan 31, 2010 at 8:34 AM, Alexander Egorenkov <
egore...@googlemail.com> wrote:
> Why doesn't 802.11 stack assign sequence numbers to A-MPDU frames ?
> When seq
ggregation queue ? Where is that queue anf how do i
use it ?
Thanks.
On Sun, Jan 31, 2010 at 4:43 AM, Sam Leffler wrote:
> Alexander Egorenkov wrote:
>
>> Sorry, i posted the wrong comment.
>> Here is the comment which i don't understand:
>>
>> /*
>>
Hi,
i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
und experimented with A-MPDU transmission. I looked into net80211 code
and there is some code which implements this feature but it worked not very
well for me.
I noticed e.g. that sequence numbers are not assigned to A-MPDU fra
o net80211
*/
Thanks.
On Wed, Jan 27, 2010 at 8:04 PM, Alexander Egorenkov <
egore...@googlemail.com> wrote:
>
> Hi,
>
> i'm implementing a device driver for a 802.11n NIC under FreeBSD 8
> und experimented with A-MPDU transmission. I looked into net80211 code
> and there is
25 matches
Mail list logo
