From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Nishank aggarwal <nishank.aggarwal89@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>
Subject: Re: Sequence Number Issue for QoS frames in 3352 SOC
Date: Sat, 2 Sep 2017 10:30:55 +0200 [thread overview]
Message-ID: <20170902083055.GB11293@redhat.com> (raw)
In-Reply-To: <CAGb8t=s+KYFnCxgMbyhGS9trujA+xdAiEwLNVEZyocHSSb-PNg@mail.gmail.com>
On Fri, Sep 01, 2017 at 04:18:36PM +0530, Nishank aggarwal wrote:
> *This is Nishank Aggarwal having 4 years of Experience in Linux Device
> Driver Development . I would like to discuss one issue i am facing in my
> current project related to WLAN 802.11 e Qos data frame.*
> *We are using 3352 SOC openwrt where i am getting one issue " STA
> re-transmitting the frames with incremented sequence number.
> <https://github.com/VivintInnovationJDM/ges-openwrt/issues/33>"*
This link seems to be wrong.
> *for Qos data frame, I paste some of the examples of sniffer logs captured.*
>
> 226269 2017-07-04 11
> <callto:226269%202017-07-04%2011>:46:42.358904 3c:4f:2d:6c:a9:e7 Netgear_3d:d5:cd QoS
> Data, SN=15, FN=0, Flags=.p..TC 15
>
> 226272 2017-07-04 11
> <callto:226272%202017-07-04%2011>:46:42.358904 3c:4f:2d:6c:a9:e7 Netgear_3d:d5:cd QoS
> Data, SN=16, FN=0, Flags=.p..R..TC 16 Frame is being
> retransmitted226279 2017-07-04 11
> <callto:226279%202017-07-04%2011>:46:42.366403 3c:4f:2d:6c:a9:e7 Netgear_3d:d5:cd QoS
> Data, SN=17, FN=0, Flags=.p..R..TC 17 Frame is being retransmitted
>
> *I know QoS data frames are generated in mac layer but i am not aware
> about where re-transmission of QoS data frames is taken care. I would
> like to know how the re-transmission frame are generated for the QoS data
> in the 3352 SOC. *
Data frames are retransmitted by the hardware. If sequence numbers
are incorrectly increased, it can be hardware or firmware bug,
but is also possible that some HW register is not correctly
programmed by the driver.
Stanislaw
parent reply other threads:[~2017-09-02 8:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGb8t=s+KYFnCxgMbyhGS9trujA+xdAiEwLNVEZyocHSSb-PNg@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170902083055.GB11293@redhat.com \
--to=sgruszka@redhat.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishank.aggarwal89@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox