Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal@plouf.fr.eu.org>
To: netfilter@vger.kernel.org
Subject: Re: iptables Qu2: how to specify !dst:port
Date: Fri, 12 Jul 2013 15:07:22 +0200	[thread overview]
Message-ID: <51DFFF8A.7040601@plouf.fr.eu.org> (raw)
In-Reply-To: <51DFF160.1050607@die-optimisten.net>

Die Optimisten a écrit :
> 
> Do I get a loop if I
> iptables -t nat -D PREROUTING  -p tcp -d 0.0.0.0:443  -j DNAT
> --to-destination 127.0.0.1:443

No. By the way, this rule may not have the intended effect.
Packets received from the outside will be seen with a loopback
destination address and discarded by the routing decision.
Packets sent over loopback skip the nat PREROUTING chain.

> Can I generally generate (kernel-hanging) loops with -nat , or is this
> recognized/inhibited ?

Not directly in the kernel, because, as I wrote above, packets sent over
loopback skip the nat PREROUTING chain.

      reply	other threads:[~2013-07-12 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 12:06 iptables Qu2: how to specify !dst:port Die Optimisten
2013-07-12 13:07 ` 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=51DFFF8A.7040601@plouf.fr.eu.org \
    --to=pascal@plouf.fr.eu.org \
    --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