From: JeongHwan Kim <frog007.kernel.kr@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: TCP syn flooding protection
Date: Fri, 23 Apr 2021 15:45:54 +0900 [thread overview]
Message-ID: <0485e030-c915-14fa-5bff-c0a0895c295b@gmail.com> (raw)
Hi, everyone
I'm testing packet flooding test with old kernel version 2.6.30.
My board experienced process starvation when injecting ICMP flood with hping3 tool.
I modified softirq invocation routine to launch ksoftirqd instead of executing do_softirq
and I limitted the speed of ethernet phy to accept below 10Mbps.
It seems that the board can process flooding ICMP packets of 10Mbps,
but the board cannot process against TCP/UDP packet flooding,
the speed of processes become slow down.
IPtabls of which rule is dropping all TCP/UDP packet does not improve the situation.
How can I protect the TCP/UDP flooding in my environment.
Thanks in advance.
Kim
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2021-04-23 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 6:45 JeongHwan Kim [this message]
2021-04-23 8:19 ` TCP syn flooding protection Valdis Klētnieks
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=0485e030-c915-14fa-5bff-c0a0895c295b@gmail.com \
--to=frog007.kernel.kr@gmail.com \
--cc=kernelnewbies@kernelnewbies.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