All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kamil Jońca" <kjonca@op.pl>
To: netfilter@vger.kernel.org
Subject: Re: exclude named sets
Date: Fri, 20 May 2022 06:32:23 +0200	[thread overview]
Message-ID: <87y1ywhlig.fsf@alfa.kjonca> (raw)
In-Reply-To: <CAMsxNkSkjBkwS=AhJpG+GPTfz1nYsH4YjLVJ56DxvW9hAVeoCg@mail.gmail.com> (Andrew Clark's message of "Fri, 20 May 2022 06:49:10 +0300")

Andrew Clark <andrewclarkii@gmail.com> writes:

> I use Debian 11 as my home router, and I have a script for workaround
> blocked addresses. Alas Roskomnadzor lists are getting bigger, so I
> came to the simple thought that it would be much easier to route all
> traffic in the TOR network, but I have a bunch of addresses which
> should be passed directly, without using TOR.
>
> This is valid rule: iifname $int_ifs ip daddr @rkn meta l4proto tcp
> redirect to :9051
> But this one is not: iifname $int_ifs ip daddr != { @akamai,
> @stormwall } meta l4proto tcp redirect to :9051

What do you mean "not valid?" You got error, or rule does not work as
expected?


Can you try:

--8<---------------cut here---------------start------------->8---
iifname $int_ifs ip daddr != @akamai meta l4proto tcp redirect to :9051
--8<---------------cut here---------------end--------------->8---
?
I suspect that problem is with "{ @akamai, @stormwall }" construct and not with
exclusion.

>
> How to exclude couple of named sets properly?
KJ

-- 
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html

  reply	other threads:[~2022-05-20  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  3:49 exclude named sets Andrew Clark
2022-05-20  4:32 ` Kamil Jońca [this message]
2022-05-20 10:57 ` Benno
  -- strict thread matches above, loose matches on Subject: below --
2022-05-20  9:01 Andrew Clark
2022-05-20  9:10 ` Kamil Jońca
2022-05-20 11:04 Andrew Clark
2022-05-30  8:10 ` Robert Sander

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=87y1ywhlig.fsf@alfa.kjonca \
    --to=kjonca@op.pl \
    --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.