From: "Tor Inge Kloumann" <toringe@casa.linuxnation.no>
To: lartc@vger.kernel.org
Subject: [LARTC] Transparent bridging / smart rate limiting
Date: Tue, 01 Jan 2002 00:25:38 +0000 [thread overview]
Message-ID: <marc-lartc-103318552500344@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
I've decided to try to make a transparent bridge, that should drop
packet's based on some weird rules.
I have googled around a bit and couldn't find any information about what
I would like to do.
And therefore I now send a mail to this mailinglist in hope that someone
can either help me, or point me in the right direction.
What I want to do is the following:
Make a transparent bridge that starts dropping ICMP packets that are
oversized(malicious icmp), drop all syn packets that comes from spoofed
hosts(non existent ip's), drop other obvious malicious traffic.
My problem is not dropping packets(hehe), the problem is dropping
packets based on these rules, so that legit icmp/syn traffic etc will
not be affected by the rules.
I've done some testing with hogwash as transparent bridge to intercept
and block malicious packets. I was however not able to use hogwash to
drop icmp/syn based on above clearified rules.
If someone could point me in the right direction/maybe someone has some
examples(?) I would be very greatfull.
Thanks in advance for any help.
Your's,
Tor Inge Kloumann
Stfu-certified engineer
[-- Attachment #2: Type: text/html, Size: 6251 bytes --]
next reply other threads:[~2002-01-01 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-01 0:25 Tor Inge Kloumann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-28 10:06 [LARTC] Transparent bridging / smart rate limiting Stef Coene
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=marc-lartc-103318552500344@msgid-missing \
--to=toringe@casa.linuxnation.no \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox