From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: netfilter@lists.netfilter.org
Subject: Gigabit filtering
Date: Wed, 5 Mar 2003 15:08:54 +0100 [thread overview]
Message-ID: <20030305140854.GG3252@puariko.nirvana> (raw)
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
We would like to setup a netfilter based firewall in front of a Gigabit
connection to the main campus backbone. Would someone on this list want to
share his experience?
A duplex Gigabit NIC has nominally a throughput of 250MB/sec. Doing this for
both directions (intern <-> extern) doubles the internal traffic bandwidth to
500MB/sec. Even PCI64/66MHz has a nominal max. throughput of 528 MB/sec, so
this is scratching the limit.
What are the solutions?
o Dual-port NICs with zerocopy for avoiding PCI traffic (I have seen some
expensive ones from Intel). Can those dual-port NICs zerocopy from one port
to the other? Is that supported from linux/netfilter?
o Multiple PCI-busses with one NIC per bus?
Any hardware recommendations? :)
Thanks!
--
Axel.Thimm@physik.fu-berlin.de
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2003-03-05 14:08 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=20030305140854.GG3252@puariko.nirvana \
--to=axel.thimm@physik.fu-berlin.de \
--cc=netfilter@lists.netfilter.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