All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Don Hughes" <support@microtechniques.com>
To: netfilter@lists.netfilter.org
Subject: DNATing back to the same network
Date: Thu, 13 Jan 2005 14:26:07 -0500	[thread overview]
Message-ID: <41E684FF.13943.7EDFCC@localhost> (raw)
In-Reply-To: <20050113165624.C0BFA5F67@mail.microtechniques.com>

 
> Message: 1
> Date: Thu, 13 Jan 2005 15:42:33 +0100 (CET)
> From: danci@agenda.si
> Subject: DNATing back to the same network
> To: netfilter@lists.netfilter.org
> Message-ID: <Pine.LNX.4.58.0501131538030.16403@desktop.agenda.si>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> 
> Hi!
> 
> I have a firewall with a number of DNAT rules for various ports/hosts.
> It would be good if local users could use the same DNAT's. However, as
> it seems this doesn't work.
> 
> My firewall has a public IP. Some ports on this IP are DNATed to
> different hosts on the local network. DNAT works for users that
> connect from the internet.
> 
> However, when a local users tries to connect to the public IP and
> DNATed port, the connection fails. Which is basically logical as the
> server receives a packet with the source IP of the actual user and it
> answeres directly to that IP.
> 
> Is it possible to change netfilter behaviour? Any other work-around
> for that?
> 

I have a POSTROUTING rule for any internal traffic to SNAT it so 
that it returns back to the router instead of directly to the 
user.




-- 
..don

dhughes@microtechniques.com
White Plains, NY




       reply	other threads:[~2005-01-13 19:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050113165624.C0BFA5F67@mail.microtechniques.com>
2005-01-13 19:26 ` Don Hughes [this message]
2005-01-13 20:17   ` DNATing back to the same network danci
2005-01-13 22:49     ` Charlie Brady
2005-02-09  8:43 Ian! D. Allen
  -- strict thread matches above, loose matches on Subject: below --
2005-01-13 14:42 danci
2005-01-13 15:35 ` Charlie Brady
2005-01-13 15:56 ` Samuel Jean
2005-02-17 17:31   ` Mohammad Khan

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=41E684FF.13943.7EDFCC@localhost \
    --to=support@microtechniques.com \
    --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.