From: "Giacomo A. Catenazzi" <cate@debian.org>
To: netfilter@lists.netfilter.org
Subject: connectionless port forwarding
Date: Fri, 24 Feb 2006 14:03:24 +0100 [thread overview]
Message-ID: <43FF041C.4050005@debian.org> (raw)
Hello.
I'm searching if I can do (or why not) a connectionless
port forwarding. Google didn't help me, and now I'm
using a std port forwarding using nat tables, but
a smaller solution is better IMHO.
I admin an "high" traffic web site. In last time there was
an huge increment of web-spam/blog-spam traffic, which I would
avoid.
I want to direct traffic from a blacklist into
an other port, so that a simple http server will
advise user (and offer a graphical challenge) to unblock.
Practically I want to mangle the port of blacklist-originated
packets, from 80 to 81, and the opposite for outgoing traffic.
Port 81 will be firewalled from extern, so I think there cannot
be problem with connection identification / collision.
Would it be possible?
Would it be lighter than std nat solution (and conncetion tracking)?
Are there already some netfilter module? (or
i should implement myself one?)
ciao
cate
PS: please CC: me. It is easier to reply
next reply other threads:[~2006-02-24 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 13:03 Giacomo A. Catenazzi [this message]
2006-02-28 14:06 ` connectionless port forwarding Rob Sterenborg
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=43FF041C.4050005@debian.org \
--to=cate@debian.org \
--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