From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Send local traffic to a different server.
Date: Thu, 24 Jun 2004 09:46:22 +0100 [thread overview]
Message-ID: <200406240946.22212.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <5EDC9B3CC8401E4184D3B43B75A75C2B46D668@mx.p21.com>
On Wednesday 23 June 2004 4:26 pm, Aldo Lagana wrote:
> am i wrong or can you not send traffic to another server simply with
> netfilter/iptables rules? Does not that require iproute2? In other words
> don't all of the rules assume that the NAT addresses are bound to local
> interfaces?
No, you can use any address you like in nat rules (both SNAT and DNAT).
Whether or not it makes sense is another matter (eg: do the packets get routed
back through the machine and get reverse-natted?), however netfilter will
allow you to specify whatever you like.
Regards,
Antony.
--
Software development can be quick, high quality, or low cost.
The customer gets to pick any two out of three.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-24 8:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 15:26 Send local traffic to a different server Aldo Lagana
2004-06-24 8:46 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 14:08 Brett Simpson
2004-06-23 13:33 ` Antony Stone
2004-06-23 14:33 ` Brett Simpson
2004-06-23 14:00 ` Antony Stone
2004-06-23 15:12 ` Brett Simpson
2004-06-23 14:24 ` Antony Stone
2004-06-23 16:41 ` Brett Simpson
2004-06-24 18:27 ` Brett Simpson
2004-06-23 14:20 ` John A. Sullivan III
2004-06-23 14:58 ` Antony Stone
2004-06-23 16:34 ` Brett Simpson
2004-06-23 15:39 ` B. McAninch
2004-06-23 16:53 ` Brett Simpson
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=200406240946.22212.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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