From: Philip Craig <philipc@snapgear.com>
To: "Horton, Dave" <dhorton@pactolus.com>
Cc: Jan Engelhardt <jengelh@medozas.de>, netfilter-devel@vger.kernel.org
Subject: Re: been a while...what happened to NFC_ALTERED?
Date: Fri, 26 Sep 2008 11:32:28 +1000 [thread overview]
Message-ID: <48DC3BAC.2090609@snapgear.com> (raw)
In-Reply-To: <E8E029BA163C694484CFEA4914619EA206853DA5@pcsexch-bknet>
Horton, Dave wrote:
> This is all in the context of a single-purpose, specialized server that
> I build which does a very specific packet forwarding task. I control
> the whole server (no other software needs to run on it) so hopefully I
> can somewhat control interactions. Regardless of the fact that it is
> non-standard, it does what I need and I need to somehow create that same
> functionality under 2.6, if possible. Do you think I should be looking
> at some sort of alternative approach? The simplest way to describe what
> I need to do is that I need to receive UDP packets on a specified set of
> ports and send them to a specified remote address:port after changing
> the source ip address:port to my local address and a specified port.
Standard nat rules can do that:
iptables -t nat -A PREROUTING -p udp --dport start:end -j DNAT --to-destination newdest:newdestport
iptables -t nat -A POSTROUTING -p udp -d newdest --dport newdestport -j SNAT --to-source newsrc:newsrcport
next prev parent reply other threads:[~2008-09-26 1:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 22:38 been a while...what happened to NFC_ALTERED? Dave Horton
2008-09-25 23:38 ` Jan Engelhardt
2008-09-26 0:47 ` Horton, Dave
2008-09-26 1:12 ` Jan Engelhardt
2008-09-26 1:28 ` Horton, Dave
2008-09-26 1:32 ` Philip Craig [this message]
2008-09-26 1:38 ` Horton, Dave
2008-09-26 4:16 ` Philip Craig
2008-09-28 15:06 ` Horton, Dave
2008-09-26 1:04 ` Philip Craig
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=48DC3BAC.2090609@snapgear.com \
--to=philipc@snapgear.com \
--cc=dhorton@pactolus.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@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.