All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Mahurin <dmahurin@dma.org>
To: netfilter-devel@lists.netfilter.org
Subject: New netfilter modules: RELAY, SOURCE, DEST
Date: Fri, 04 Jun 2004 16:33:22 -0700	[thread overview]
Message-ID: <40C106C2.3050605@dma.org> (raw)

I have written some new netfilter/iptables modules that do the following:

RELAY - smart UDP relay, that learns and relays packets from and to the 
endpoint pair that connect to each port in a specified range. The 
source, destination and checksums of relayed packets are adjusted. This 
is useful for servers that act as a middle man in a large number of UDP 
data connections. A /proc interface is implemented to manage ports. The 
/proc interface replaced a netlink interface which remains in the driver.
I have tested the RELAY for about 2000 bi-directional channels with over 
900Mbs of data.

SOURCE - mangles packets changing the source address without the 
overhead and connection tracking associated with NAT.

DEST - mangles packets changing the destination address without the 
overhead and connection tracking associated with NAT.

I have put together the changes in patch-o-matic-ng format, but I am not 
sure where to send that.

http://berkeley.innomedia.com/pub/source/ipt_relay/
http://berkeley.innomedia.com/pub/source/ipt_relay/README.txt
http://berkeley.innomedia.com/pub/source/ipt_relay/linux/patch-o-matic-ng/

Note that currently, the RELAY module requires an allow-spoofing patch, 
as when RELAY is used normally in PREROUTING, it changes the destination 
to the other endpoint and the source to itself. Then the spoofing check 
code sees this as an external packet pretending to be itself.

-don

                 reply	other threads:[~2004-06-04 23:33 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=40C106C2.3050605@dma.org \
    --to=dmahurin@dma.org \
    --cc=netfilter-devel@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 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.