From: "Марк Коренберг" <socketpair@gmail.com>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org,
kadlecsik.jozsef@wigner.hu, kadlec@sunserv.kfki.hu
Subject: ipset hash:net:port:net
Date: Thu, 22 Jun 2023 17:50:43 +0300 [thread overview]
Message-ID: <CAEmTpZGTbHcd84vA5VL6FfDc8+n+E0VMt+GpPkVLw5Vijp5iLA@mail.gmail.com> (raw)
Hi everyone.
1. In the latest ipset, adding "1.2.3.4/0,tcp:0,1.2.3.0/24" is not
allowed. I would like it to be allowed. It should match on any TCP
traffic that matches source and destination.
2. The same for protocol number 0. I want "1.2.3.4/0,0:0,1.2.3.0/24"
to match all traffic that matches source and destination.
These requirements come from the real cases, where an administrator
adds rules to control access to his networks.
Is it possible to make such changes? TCP port 0 is not real thing, as
well as IP protocol 0. So we can give them special meaning in IPSets.
although icmp:0 is not so clear in this case. Possibly allow to set -1
? as protocol or port for matching any ?
--
Segmentation fault
next reply other threads:[~2023-06-22 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 14:50 Марк Коренберг [this message]
2023-06-23 18:30 ` ipset hash:net:port:net Jozsef Kadlecsik
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=CAEmTpZGTbHcd84vA5VL6FfDc8+n+E0VMt+GpPkVLw5Vijp5iLA@mail.gmail.com \
--to=socketpair@gmail.com \
--cc=kadlec@blackhole.kfki.hu \
--cc=kadlec@sunserv.kfki.hu \
--cc=kadlecsik.jozsef@wigner.hu \
--cc=netfilter-devel@vger.kernel.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).