From: pauloric@contatogs.com.br
To: netfilter <netfilter@vger.kernel.org>
Subject: meta day not working
Date: Sat, 6 Jun 2020 10:10:05 -0300 (BRT) [thread overview]
Message-ID: <269506832.599.1591449005072.JavaMail.zimbra@contatogs.com.br> (raw)
In-Reply-To: <000d2e24-1df3-c42a-3117-05d6390194e8@softtalker.com>
Hi all
Hope that everyone is working safety at home.
I have been trying to use meta date , but is not working. I think I could not find the correct syntax, but at list I tried in many tentatives.
Ubuntu server 20.04
kernel 5.6.0-1010-oem and 5.4.0-33-generic
nftables 0.9.3-2 amd64
libnftnl11 1.1.5-1
libnftables1 0.9.3-2
libnfnetlink0 1.0.1-3build1
Not working:
only meta day
/etc/nftables.d/gerais:17:168-176: Error: Could not parse Day of week of packet reception
add rule inet filter INPUT ip saddr 192.168.0.0/16 meta iifname "wan1" ip protocol tcp tcp dport {53,88,123,135,139,389,445,464,636,3268,3269,5353,1024-5000} meta day "(1,3,5)" counter accept comment "ttttttt"
meta day and meta hour
/etc/nftables.d/gerais:2:189-193: Error: Could not parse Day of week of packet reception
add rule inet filter INPUT ip saddr 192.168.0.0/16 ip daddr 192.168.10.1 meta iifname "lan" ip protocol tcp tcp dport {53,88,123,135,139,389,445,464,636,3268,3269,5353,1024-5000} meta day "1,2" meta hour "8:0" - "18:0" counter accept comment "xxx"
Work if I change meta day and let only one day.
ip saddr 192.168.0.0/16 ip daddr 192.168.10.1 iifname "lan" ip protocol tcp tcp dport { 53, 88, 123, 135, 139, 389, 445, 464, 636, 1024-5000, 5353 } meta day "Monday" meta hour "08:00"-"18:00" counter packets 0 bytes 0 accept comment "xxx"
ip saddr 192.168.0.0/16 iifname "wan1" ip protocol tcp tcp dport { 53, 88, 123, 135, 139, 389, 445, 464, 636, 1024-5000, 5353 } meta day "Wednesday" counter packets 0 bytes 0 accept comment "ttttttt"
What am I doing incorrectly...?
Can't I use more than 1 day in rule _+ time ?
I intend use meta day + meta time as normaly this:
Monday to Friday from 8:00 until 18:00hs.
Thanks for you time
best regards
--
Paulo Ricardo Bruck consultor
next prev parent reply other threads:[~2020-06-06 13:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 14:06 nftables: Strange Error When Adding Element to Named Set Mike Dillinger
2020-05-08 16:01 ` Pablo Neira Ayuso
2020-05-08 17:13 ` Mike Dillinger
2020-05-31 17:18 ` Mike Dillinger
2020-06-01 12:41 ` Pablo Neira Ayuso
2020-06-01 14:58 ` Mike Dillinger
2020-06-01 15:48 ` Stefano Brivio
2020-06-01 16:13 ` Mike Dillinger
2020-06-01 16:07 ` Mike Dillinger
2020-06-02 13:28 ` Mike Dillinger
2020-06-02 14:25 ` Stefano Brivio
2020-06-02 16:38 ` Stefano Brivio
2020-06-02 19:58 ` Mike Dillinger
2020-06-06 13:10 ` pauloric [this message]
2020-06-06 14:37 ` meta day not working Florian Westphal
2020-06-06 15:06 ` pauloric
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=269506832.599.1591449005072.JavaMail.zimbra@contatogs.com.br \
--to=pauloric@contatogs.com.br \
--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