Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74970 - [nftables] version 1.0.3 breaks set evaluation in config files

Attached to Project: Arch Linux
Opened by Kyle Brady (Shasta) - Monday, 06 June 2022, 06:19 GMT
Last edited by Christian Hesse (eworm) - Tuesday, 07 June 2022, 13:48 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

nftables 1.0.3 has broken support for set evaluation in some configuration files.

This has been reported upstream, and is fixed by:

https://git.netfilter.org/nftables/commit/?id=818f7dded9c9e8a89a2de98801425536180ae307

I figured I should report this here after spending quite a while trying to debug
the very poor error message, and since this is potentially leaving folks without
a firewall running upon restarting.

This task depends upon

Closed by  Christian Hesse (eworm)
Tuesday, 07 June 2022, 13:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  nftables 1:1.0.3-2
Comment by Webhostbudd (Webhostbudd) - Monday, 06 June 2022, 22:25 GMT
Likewise, this broke my router and I had to manually revert to 1.0.2. Fix looks good to me
Comment by Morten Linderud (Foxboron) - Tuesday, 07 June 2022, 13:20 GMT
Please try 1:1.0.3-2 in `[testing]`
Comment by Philipp Richter (popsUlfr) - Tuesday, 07 June 2022, 13:28 GMT
I was getting cryptic errors like:

```
/etc/nftables.conf:20:14-24: Error: Could not resolve service: Servname not supported for ai_socktype
ct state { established, related } counter accept
^^^^^^^^^^^
```

1.0.3-2 from testing fixes the issue thanks!
Comment by Lubomir Krajcovic (scott32) - Tuesday, 07 June 2022, 13:39 GMT
I confirm 1.0.3-2 fixes this.

Loading...