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!
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!
FS#43939 - [nftables] backport to stable request to fix broken jump to chains
Attached to Project:
Arch Linux
Opened by Alex Pilon (alp) - Tuesday, 24 February 2015, 23:09 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 25 February 2015, 04:23 GMT
Opened by Alex Pilon (alp) - Tuesday, 24 February 2015, 23:09 GMT
Last edited by Sébastien Luttringer (seblu) - Wednesday, 25 February 2015, 04:23 GMT
|
DetailsDescription:
Upstream commit 454ffab9cc695b9618324a6a0a4dead6d5289f8d (rule: fix object order via nft -f) is required to unbreak certain nftables idioms. Cherry-picked the commit in question onto tag v0.4 from upstream, and it seems to compile and work so far. Applies to version 0.4. Steps to reproduce: # cat > ruleset << EOF table inet test { chain ipv4-chain { } chain ipv6-chain { } chain input { type filter hook input priority 0; meta nfproto vmap { ipv4: jump ipv4-chain, ipv6: jump ipv6-chain } } } EOF # nft -f ruleset ruleset:1:1-2: Error: Could not process rule: No such file or directory table inet test { ^^ |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Wednesday, 25 February 2015, 04:23 GMT
Reason for closing: Fixed
Additional comments about closing: nftables-1:0.4-4
Wednesday, 25 February 2015, 04:23 GMT
Reason for closing: Fixed
Additional comments about closing: nftables-1:0.4-4