From: Martijn Lievaart <m@rtij.nl>
To: msn@vtopia.co.kr
Cc: netfilter@vger.kernel.org
Subject: Re: Completely DROP for UDP packets.
Date: Sat, 08 Dec 2007 21:34:54 +0100 [thread overview]
Message-ID: <475AFFEE.5010906@rtij.nl> (raw)
In-Reply-To: <1368.121.163.60.159.1197142746.squirrel@211.111.194.2>
msn wrote:
> Hi, I'm trying to dropping all UDP packets from specific address
> but it still has higher CPU usages. anyone has ideas for this
> issues ? here's example
>
> A --+---> F
> B --+
> C --+
>
> A/B/C sending massive UDP packets to F, also it has address dropping
> rules fro A/B/C. Yes, it is works fine. But if i see the CPU usages
> of 'F' some of cases it is using more than 20-30% when its(A/B/C)
> sending 100M to F. is there any best way to decreasing the CPU usage
> of the 'F' ? thanks in advance.
>
> Cheers.
>
> P.S :
> 1. INPUT filter dropping very higher CPU usages
> 2. TARPIT and prestate PREROUTING dropping less higher but not satisfied.
>
>
TARPITTING does not work on UDP, it's for TCP only. Just DROP in the raw
table.
HTH,
M4
next prev parent reply other threads:[~2007-12-08 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 19:39 Completely DROP for UDP packets msn
2007-12-08 20:34 ` Martijn Lievaart [this message]
2007-12-10 5:43 ` msn
2007-12-10 5:45 ` msn
2007-12-10 15:17 ` Pascal Hambourg
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=475AFFEE.5010906@rtij.nl \
--to=m@rtij.nl \
--cc=msn@vtopia.co.kr \
--cc=netfilter@vger.kernel.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