All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bgs <bgs@bgs.hu>
To: Netfilter <netfilter@lists.netfilter.org>
Subject: Problem with SNAT
Date: Thu, 02 Sep 2004 20:57:18 +0200	[thread overview]
Message-ID: <41376D0E.3070208@bgs.hu> (raw)


  Greetings,

I have problems with the following setup:

A linux with two NICs. One with IP of 10.0.2.2 and one with 10.0.3.57.
I have DNAT-ed traffic coming in on the 10.0.2.2 that was originally 
sent to 10.0.2.1. (Another node doing the DNAT). I have problems on the 
route back so I decided to SNAT the backward udp traffic to  soource 
10.0.2.1 and send the SNATed packets back on another route.

I added the line to nat postrouting (-d target_net -s 10.0.2.2 -p udp -j 
SNAT --to-source 10.0.2.1) but the packages don't even seem to hit the 
nat postrouting chain. Let alone my SNAT rule.

Any ideas what could be wrong ?

Thanks
Bgs




             reply	other threads:[~2004-09-02 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02 18:57 Bgs [this message]
2004-09-02 20:17 ` Problem with SNAT Jason Opperisano
2004-09-03 11:06   ` Alistair Tonner
2004-09-03 17:00   ` Bgs
  -- strict thread matches above, loose matches on Subject: below --
2006-05-24 19:59 Ian Batterbee
2017-07-16 22:07 Problem with snat sorcus
2017-07-17  6:22 ` Arturo Borrero Gonzalez
2017-07-17 12:50   ` sorcus

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=41376D0E.3070208@bgs.hu \
    --to=bgs@bgs.hu \
    --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.