From: Carsten Aulbert <carsten@welcomes-you.com>
To: netfilter@vger.kernel.org
Subject: iptables performance good enough for 10 GBit link?
Date: Wed, 07 Nov 2007 21:03:55 +0100 [thread overview]
Message-ID: <47321A2B.10801@welcomes-you.com> (raw)
Hi,
sorry that my first posting here will be a vague one. We are currently
estimating the possibility for a computer to act as a packet filter
between 2 10Gbit links. Since we have no experience beyond 1 Gbit I
would like to ask a few questions:
(1) Has anyone tried how much data can be pumped through available 10
Gbit cards on a recent Linux kernel?
(2) How much CPU power/memory is needed by netfilter for a simple set-up
where packages on the incoming port need to be evaluated based on their
IP-range. Imaging simply allowing only ssh and NFS connections (TCP,
limited port range) from a certain /24 network and reject/drop all other
incoming packages on the external interface. So far no NAT is planned.
(3) Is this the right place to ask these questions ;)
Thanks a lot for a few hints, if this is possible or needs testing or ...
Cheers
Carsten
reply other threads:[~2007-11-07 20:03 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=47321A2B.10801@welcomes-you.com \
--to=carsten@welcomes-you.com \
--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