All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven-Haegar Koch <haegar@sdinet.de>
To: imnozi@gmail.com
Cc: netfilter@vger.kernel.org
Subject: Re: IPv4 NAT and lo, and iptables
Date: Wed, 1 May 2024 01:03:28 +0200 (CEST)	[thread overview]
Message-ID: <184bed16-17ab-d6ee-992b-2e094b639016@sdinet.de> (raw)
In-Reply-To: <20240430182200.39ac9ea1@playground>

On Tue, 30 Apr 2024, imnozi@gmail.com wrote:

> Questions:
>   - Is lo ignored in PREROUTING?
>   - Is it possible to DNAT local traffic on FW_A (changing) the public IP to
>     the private IP on LAN_2?
>   - Would I specify '-i lo' in mangle:PREROUTING and nat:PREROUTING (as I do
>     for the real NICs)?
> 
> The uber questions are:
>   - Should I be able to DNAT and SNAT traffic on lo just as I can on other
>     LANs, or do I need to take extra steps?

Locally generated traffic does not pass nat PREROUTING chain - you need 
to add matching DNAT rules to the nat OUTPUT chain if you want dnat 
rewriting applied to it.

And similar traffic targetting the local system (after DNAT) does not 
pass POSTROUTING, if you want such traffic SNAT'ed you need to use the 
nat INPUT chain.

>   - Is this a known oddity? or was it known back around Linux 3.16 and
>     iptables 1.6? (Don't ask; sometimes we're stuck in a place we don't
>     want to be.)

c'ya
sven-haegar

-- 
Three may keep a secret, if two of them are dead.
- Ben F.

  reply	other threads:[~2024-04-30 23:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 22:22 IPv4 NAT and lo, and iptables imnozi
2024-04-30 23:03 ` Sven-Haegar Koch [this message]
2024-05-01  0:46   ` imnozi

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=184bed16-17ab-d6ee-992b-2e094b639016@sdinet.de \
    --to=haegar@sdinet.de \
    --cc=imnozi@gmail.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 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.