From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Bradley Hook <bhook@kansasdeaf.gov>
Cc: netfilter@vger.kernel.org
Subject: Re: Packets not traversing postrouting chain
Date: Mon, 31 Mar 2025 18:51:46 +0200 [thread overview]
Message-ID: <Z-rIIhraCyG8KELs@calendula> (raw)
In-Reply-To: <CAPrh4R458ZB8C5-Zm52FsnyGQMQv2EBp-pvkQ2wcZSeHhtoeNg@mail.gmail.com>
On Mon, Mar 31, 2025 at 11:19:31AM -0500, Bradley Hook wrote:
[...]
> The issue we are seeing is that packets from 192.168.122.252 to
> 8.8.8.8 are not traversing the postrouting chain at all. We can see
> the packets leaving the interface without NAT applied. We can see the
> packets hitting the forward chain with the trace. Other traffic from
> other subnets are being masqueraded just fine. We just aren't seeing
> the packets from 192.168.122.x/24 hit any postrouting rules at all.
Can you check if connection tracking is tagging these packets as
invalid?
next prev parent reply other threads:[~2025-03-31 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 16:19 Packets not traversing postrouting chain Bradley Hook
2025-03-31 16:51 ` Pablo Neira Ayuso [this message]
2025-03-31 17:00 ` Bradley Hook
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=Z-rIIhraCyG8KELs@calendula \
--to=pablo@netfilter.org \
--cc=bhook@kansasdeaf.gov \
--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;
as well as URLs for NNTP newsgroup(s).