ath9k-devel.lists.ath9k.org archive mirror
 help / color / mirror / Atom feed
From: SangHyuk Kim <tkdgur7896@gmail.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] How to send corrupted packet using FCS/CRC ?
Date: Tue, 23 Aug 2016 22:02:33 +0900	[thread overview]
Message-ID: <CA+eadOB7cOmPqE1UME1fTPg7OhUpNAyH3h2vtaqApvm3Wp0FKA@mail.gmail.com> (raw)

Hi all,

I have tried to send corrupted packet using FCS/CRC.
I'm using ath9k-ar9003 driver and I inserted AR_CorruptFCS to ar9003_mac.c.
Also I made a switch which decides whether FCS corrupt or not using TOS
value in IP header.

I have two main problems.

*#1. How to send FCS corrupted packet to air ?*
I tested it in TCP/IP socket communication and the results are :

1) Normal packet (non-FCS corrupt) is arrived at RX
2) Corrupt packet (FCS corrupt) is NOT shown at RX

I think when I corrupt FCS, network driver discards it until FCS be right
so corrupted packet can't be sent at TX
However, I don't know how can I fake FCS value at TX.

*#2. How can I see all the packets using wireshark monitor mode ?*
To observe packet status, I use wireshark by monitor mode.
When TX machine does something using web-browser, these can be shown on
wireshark as TCP things.
However, when TX machine sends to RX thing using TCP/IP socket program,
these are shown intermittenly.
Why all packets are not be shown on wireshark ?
Am I missing something ?

Please give any advice.
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20160823/e804b835/attachment.html 

                 reply	other threads:[~2016-08-23 13:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CA+eadOB7cOmPqE1UME1fTPg7OhUpNAyH3h2vtaqApvm3Wp0FKA@mail.gmail.com \
    --to=tkdgur7896@gmail.com \
    --cc=ath9k-devel@lists.ath9k.org \
    /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;
as well as URLs for NNTP newsgroup(s).