From: Henrik Nordstrom <henrik@henriknordstrom.net>
To: Balazs Scheidler <bazsi@balabit.hu>
Cc: Jan Engelhardt <jengelh@medozas.de>,
KOVACS Krisztian <hidden@sch.bme.hu>,
Andrey Luzgin <andrey@icomsw.com>,
tproxy@lists.balabit.hu, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [tproxy] udp + tproxy
Date: Thu, 13 Nov 2008 09:44:54 +0100 [thread overview]
Message-ID: <1226565894.13986.5.camel@henriknordstrom.net> (raw)
In-Reply-To: <1226561154.15193.10.camel@bzorp.balabit>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On tor, 2008-11-13 at 08:25 +0100, Balazs Scheidler wrote:
> PS: I was talking to Patrick McHardy whether to send the udp_accept()
> patch for kernel inclusion, he said it might be worth trying, however he
> was not completely sure it'd be integrated. So I didn't push it so far.
I second this, but also think that it will see some initial resistance.
I guess the main complaint (assuming code is in good shale) will be that
UDP does not have any sender verification, which means it's very easy to
flood the kernel with UDP "connection requests". But on the other hand
there is also no SYN_RECV or FIN_WAIT/TIME_WAIT states which may hold up
things beyond CPU processing speed so this is not by far as big problem
to deal with as in the TCP case..
Regards
Henrik
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 307 bytes --]
prev parent reply other threads:[~2008-11-13 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1226490030.31896.12.camel@sysandrey.icomswg.local>
[not found] ` <20081112185910.GA1793@sch.bme.hu>
2008-11-12 19:27 ` [tproxy] udp + tproxy Balazs Scheidler
2008-11-13 7:17 ` Jan Engelhardt
2008-11-13 7:25 ` Balazs Scheidler
2008-11-13 8:44 ` Henrik Nordstrom [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=1226565894.13986.5.camel@henriknordstrom.net \
--to=henrik@henriknordstrom.net \
--cc=andrey@icomsw.com \
--cc=bazsi@balabit.hu \
--cc=hidden@sch.bme.hu \
--cc=jengelh@medozas.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=tproxy@lists.balabit.hu \
/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