netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yadunandan Pillai <ytpillai@gmail.com>
To: w@1wt.eu
Cc: netdev@vger.kernel.org, thesw4rm@pm.me
Subject: Re: Verify ACK packets in handshake in kernel module (Access TCP state table)
Date: Sat, 21 Sep 2019 00:18:01 -0400	[thread overview]
Message-ID: <c52c510d-ad44-c842-319f-f8feb5edf7e6@gmail.com> (raw)
In-Reply-To: <20190921031529.GG1889@1wt.eu>

You're right. I clearly need to be more aware of where I am looking. I think I got tripped up because I was trying to only look at header files like a noob. There is a tcp_ack function there with flags for this purpose. Appreciate it!

Just one question, would it be acceptable to directly include the C file in a kernel module?


      reply	other threads:[~2019-09-21  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 23:43 Verify ACK packets in handshake in kernel module (Access TCP state table) Swarm
2019-09-21  3:15 ` Willy Tarreau
2019-09-21  4:18   ` Yadunandan Pillai [this message]

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=c52c510d-ad44-c842-319f-f8feb5edf7e6@gmail.com \
    --to=ytpillai@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=thesw4rm@pm.me \
    --cc=w@1wt.eu \
    /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).