From: "Eliezer Croitor" <ngtech1ltd@gmail.com>
To: netfilter@vger.kernel.org
Subject: RE: [nftables] granular rule for combined tcp & udp sports?
Date: Fri, 9 Oct 2020 09:23:26 +0300 [thread overview]
Message-ID: <000101d69e04$b3965540$1ac2ffc0$@gmail.com> (raw)
In-Reply-To: <8bf8c296-8857-03c7-9d04-463a7e9a1e6e@gmx.net>
What OS and nftables versions are you using?
----
Eliezer Croitoru
Tech Support
Mobile: +972-5-28704261
Email: ngtech1ltd@gmail.com
-----Original Message-----
From: ѽ҉ᶬḳ℠ <vtol@gmx.net>
Sent: Tuesday, October 6, 2020 9:49 AM
To: netfilter@vger.kernel.org
Cc: Yuval Steuer <yuvalsteuer11@gmail.com>
Subject: Re: [nftables] granular rule for combined tcp & udp sports?
Thank you for the input but that still prints an (yet another) error:
Error: syntax error, unexpected !=, expecting ')'
On 06/10/2020 05:42, Yuval Steuer wrote:
> ((tcp sport != { 80, 443, 993, 5228 }) or (udp sport != 19302) and
> (ip6 saddr @g_6))
>
> On Mon, 5 Oct 2020 at 16:02 ѽ҉ᶬḳ℠ <vtol@gmx.net <mailto:vtol@gmx.net>>
> wrote:
>
> I am trying to get a granular logging rule going, combining tcp
> and udp
>
> sports for ip6 saddr but somehow failing:
>
>
>
>
>
> tcp sport != { 80, 443, 993, 5228 } udp sport != 19302 ip6 saddr @g_6
>
> log flags all prefix "G_C :" continue
>
>
>
> -> Error: conflicting protocols specified: tcp vs. udp
>
>
>
>
>
>
>
> ip6 saddr @g_6 tcp sport != { 80, 443, 993, 5228 } | udp sport !=
> 19302
>
> log flags all prefix "G_C :" continue;
>
>
>
> -> Error: syntax error, unexpected '|', expecting newline or semicolon
>
>
>
next prev parent reply other threads:[~2020-10-09 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:56 [nftables] granular rule for combined tcp & udp sports? ѽ҉ᶬḳ℠
[not found] ` <CABeHSrYi=MT8pD6nsRaUK7u56UvO-E7qh1Kmo0=YU386AE8aXw@mail.gmail.com>
2020-10-06 6:49 ` ѽ҉ᶬḳ℠
2020-10-09 6:23 ` Eliezer Croitor [this message]
2020-10-06 8:31 ` Pablo Neira Ayuso
2020-10-06 8:54 ` ѽ҉ᶬḳ℠
2020-10-06 9:04 ` Pablo Neira Ayuso
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='000101d69e04$b3965540$1ac2ffc0$@gmail.com' \
--to=ngtech1ltd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox