Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Tom Fischer <tom.fischer@ebuz.de>
To: netfilter@lists.netfilter.org
Subject: Re: DNAT-Problem
Date: Thu, 9 Sep 2004 16:13:07 +0200	[thread overview]
Message-ID: <20040909161307.022ec379@nixe> (raw)
In-Reply-To: <1094736414.2044.22.camel@wolfpack.ljm.dom>

On Thu, 09 Sep 2004 09:26:54 -0400
Jason Opperisano <opie@817west.com> wrote:

> On Thu, 2004-09-09 at 07:58, Tom Fischer wrote:
> > On Thu, 09 Sep 2004 07:38:26 -0400
> > Jason Opperisano <opie@817west.com> wrote:
> > 
> > > what are the IP addresses of $oldmachine and $newmachine
> > > (obfuscate the first two octets if you must)?
> > 
> > $oldmachine=81.16.97
> > $newmachine=80.190.140
> > 
> > There are a few IP-Adresse which i have to transfer to the
> > newmachine.
> > 
> > > are you trying to DNAT from one machine on the local network to
> > > another machine on the local network?  what network is the client
> > > traffic sourcing from?  is it the same network?
> > 
> > No, they are on different locations. The old one is in Innsbruck,
> > Austria and the new one in Munich, Germany.
> 
> for what it's worth--it sounds like your problem has much more to do
> with routing than with iptables firewalling.
> 
> i think i may have misunderstood your original post.  are you running
> iptables and the DNAT rule on $oldmachine?  if so, unless the reply
> packets from $newmachine are routed back through $oldmachine; this
> setup won't work (for what should be painfully obvious reasons).

Ok, i see the Problem. Is it possible to mark this packet and route it
based on the mark? I think i build a similar setup few weeks ago where i
have to route and nat packets which came in on eone vpn and should go
out on the other vpn.

> if your DNAT rule is on a gateway machine upstream from both
> $oldmachine and $newmachine--i'd say you have a routing failure
> somewhere in the chain.

No, unfortunately it is not. I will try to mark the packets.

Thx for help

Tom



  reply	other threads:[~2004-09-09 14:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09  2:10 DNAT-Problem Tom Fischer
2004-09-09  2:26 ` DNAT-Problem Jason Opperisano
2004-09-09 10:29   ` DNAT-Problem Tom Fischer
2004-09-09 11:38     ` DNAT-Problem Jason Opperisano
2004-09-09 11:58       ` DNAT-Problem Tom Fischer
2004-09-09 13:26         ` DNAT-Problem Jason Opperisano
2004-09-09 14:13           ` Tom Fischer [this message]
2004-09-09  8:44 ` DNAT-Problem Abdul-Wahid Paterson
  -- strict thread matches above, loose matches on Subject: below --
2004-05-02 10:20 DNAT-PROBLEM persaie persaie
2004-05-02 17:19 ` DNAT-PROBLEM Antony Stone

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=20040909161307.022ec379@nixe \
    --to=tom.fischer@ebuz.de \
    --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