From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: Please help redirecting locally generated traffic
Date: Fri, 20 Jul 2007 13:10:50 -0500 [thread overview]
Message-ID: <46A0FAAA.3080203@riverviewtech.net> (raw)
In-Reply-To: <18563.192.35.79.70.1184885123.squirrel@www.dcsnow.com>
On 07/19/07 17:45, aragonx@dcsnow.com wrote:
> I have a situation where an application on my box wants to talk to
> the wrong IP address. The developers will gladly fix the bug in the
> next version but I need a quicker fix.
Typical...
> Here is the situation. I have traffic that is going to 10.0.0.1 and
> needs to got to 198.162.0.1. It's created on the machine that I need
> to do the routing on. It's a Linux machine using iptables 1.2.9.
> Neither SNAT or DNAT seem to work. DNAT wants to work on the
> incomming packets but does what I need. SNAT will work on the
> outgoing packets but doesn't do what I need. Mangle seems to only
> want to send packets to my 127.0.0.1.
Ugh. You are wanting to redirect traffic that is not following the
normal packet flow through the kernel.
> Any help would be appreciated.
Have you considered adding the 10.0.0.1 IP address to equipment with a
corresponding 10.0.0.x IP address to your system?
Or you may be able to look in to some sort of (socks?) proxy rapper that
will bind a 10.0.0.1 and allow you to redirect the traffic over to
198.162.0.1.
Grant. . . .
prev parent reply other threads:[~2007-07-20 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 22:45 Please help redirecting locally generated traffic aragonx
2007-07-20 18:10 ` Grant Taylor [this message]
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=46A0FAAA.3080203@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=gtaylor+reply@riverviewtech.net \
--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 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.