From: Andraz Sraka <a@aufbix.org>
To: lartc@vger.kernel.org
Subject: [LARTC] linux box as vlan p2p limiter and firewall?
Date: Thu, 23 Mar 2006 10:43:25 +0000 [thread overview]
Message-ID: <1143110605.17746.45.camel@localhost> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 710 bytes --]
re
I would like to do some firewalling and p2p shaping/limiting on one of
the vlans in my network and I was thinking of using linux box as
transparent bridged firewall/limiter. For this I'm planning to use AMD64
2.2Ghz box with 2 1gbit NIC (Broadcom 5721), that will be bridged. The
box must be totally transparent and unseen in the network, as well as it
should have much influence on network performance.
Can anyone give me some guidelines where to begin, how to limit/shape
p2p traffic on that vlan. Is it even doable?? Any example
htb/etables/iptables configuration script will also help. :)
thanks in advance ..
regards,
Andraz
--
BOFH excuse #362:
Plasma conduit breach
[-- Attachment #1.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 1903 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-03-23 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 10:43 Andraz Sraka [this message]
2006-03-23 15:58 ` [LARTC] linux box as vlan p2p limiter and firewall? Carlos Blanquer
2006-03-23 16:10 ` Andraz Sraka
2006-03-23 16:16 ` Andraz Sraka
2006-03-23 16:18 ` Roberto Scattini
2006-03-23 16:28 ` Philip Gaw
2006-03-23 16:29 ` Philip Gaw
2006-03-23 16:39 ` Andraz Sraka
2006-03-24 0:20 ` Jason Boxman
2006-03-24 16:54 ` Andraz Sraka
2006-03-24 17:39 ` Klaus
2006-03-24 19:07 ` Jason Boxman
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=1143110605.17746.45.camel@localhost \
--to=a@aufbix.org \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.