All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Bush <randy@psg.com>
To: Sunny73Cr <Sunny73Cr@protonmail.com>
Cc: Kerin Millar <kfm@plushkava.net>, netfilter@vger.kernel.org
Subject: Re: prefix len confusion
Date: Wed, 10 Jun 2026 17:25:08 -0700	[thread overview]
Message-ID: <m21ped2aaj.wl-randy@psg.com> (raw)
In-Reply-To: <scvzZFFc0YAE7k_JC5BL5RPJaJmJhsP5UHJ8TSZzLVAQohQAdyhlLFw3AV9_oNq6GpFaWI8x4LKNiS4NPqOUZe0gLUhx1G0oRLStKsyGyEw=@protonmail.com>

>      chain wan-in {
>          ip saddr $BOGONS4 drop
>          ip saddr $EXTv4 daddr $VULN4 accept
>          ip saddr $JUMP4 daddr $VULN4 accept
>          ip daddr $VULN4 drop
>          ip protocol icmp accept
> ...
> 
> Did you mean to do this instead?

not really.  if the source is in the trust boundary, it can access
anything.  e.g. there was also a

           tcp dport 8006 ip daddr $PROX4 drop

in there which is yet more dests allowed to trusted sources

randy

  reply	other threads:[~2026-06-11  0:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  0:10 prefix len confusion Randy Bush
2026-06-10  0:51 ` Kerin Millar
2026-06-10  1:01   ` Randy Bush
2026-06-10  1:26     ` Kerin Millar
2026-06-10  1:32       ` Randy Bush
2026-06-10  1:38         ` Kerin Millar
2026-06-10 16:33       ` Randy Bush
2026-06-10 16:53         ` Kerin Millar
2026-06-10 17:19           ` Randy Bush
2026-06-10 18:02             ` Kerin Millar
2026-06-10 23:51               ` Sunny73Cr
2026-06-10 23:57                 ` Randy Bush
2026-06-11  0:06                   ` Sunny73Cr
2026-06-11  0:25                     ` Randy Bush [this message]
2026-06-11  1:05                 ` Kerin Millar
2026-06-11  1:12                   ` Randy Bush
2026-06-10  6:20     ` Reindl Harald
2026-06-10 10:09       ` Kerin Millar
2026-06-10 16:01       ` Randy Bush

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=m21ped2aaj.wl-randy@psg.com \
    --to=randy@psg.com \
    --cc=Sunny73Cr@protonmail.com \
    --cc=kfm@plushkava.net \
    --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.