Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: Scott Bronson <bronson@rinspin.com>
Cc: netfilter <netfilter@vger.kernel.org>
Subject: Re: Packet disappears after DNAT?
Date: Sat, 19 Dec 2015 17:38:31 +0100	[thread overview]
Message-ID: <56758807.90402@plouf.fr.eu.org> (raw)
In-Reply-To: <CAKmUPx7ST01XPj+cXSWhyksFJw77xeXf-WouaQkCxZ0QG1_aWQ@mail.gmail.com>

Scott Bronson a écrit :
> 
> Good question.  Editing mistake.  I'm actually forwarding different
> ports to different guests depending on port number:
> 
> iptables -t nat -A POSTROUTING -s 192.168.122.10/32 -d
> 192.168.122.10/32 -p udp --dport 53 -j MASQUERADE
> iptables -t nat -A POSTROUTING -s 192.168.122.10/32 -d
> 192.168.122.10/32 -p tcp --dport 53 -j MASQUERADE
> iptables -t nat -A POSTROUTING -s 192.168.122.12/32 -d
> 192.168.122.12/32 -p tcp --dport 25 -j MASQUERADE

I don't think you need a separate rule for each forwarded port. One
global rule would do the job, as only forwarded packets would match the
source/destination address.


iptables -t nat -A POSTROUTING -s 192.168.122.10/32 -d 192.168.122.10/32
  -j MASQUERADE

      reply	other threads:[~2015-12-19 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04  9:43 Packet disappears after DNAT? Scott Bronson
2015-12-04 11:55 ` Anton Danilov
2015-12-04 16:18   ` Scott Bronson
2015-12-06  8:49     ` Anton Danilov
2015-12-07  6:57       ` Scott Bronson
2015-12-05 10:31 ` Pascal Hambourg
2015-12-07  7:07   ` Scott Bronson
2015-12-07  8:01     ` Pascal Hambourg
2015-12-07  8:06       ` Pascal Hambourg
2015-12-15 12:21       ` Scott Bronson
2015-12-15 13:06         ` Pablo Neira Ayuso
2015-12-15 19:49           ` Pascal Hambourg
2015-12-18  0:41           ` Scott Bronson
2015-12-19 16:34             ` Pascal Hambourg
2015-12-15 19:45         ` Pascal Hambourg
2015-12-18  0:51           ` Scott Bronson
2015-12-19 16:38             ` Pascal Hambourg [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=56758807.90402@plouf.fr.eu.org \
    --to=pascal@plouf.fr.eu.org \
    --cc=bronson@rinspin.com \
    --cc=netfilter@vger.kernel.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