aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot
diff options
context:
space:
mode:
authorBrett Mastbergen <bmastbergen@untangle.com>2018-09-12 15:04:55 -0400
committerHauke Mehrtens <hauke@hauke-m.de>2018-09-22 21:20:55 +0200
commitf57806b56e5f6ca7bb9fb66d5b175b5f98ece93c (patch)
treea852fcd9ee8d2a1746baff1b4a8e8f07501d8e91 /package/boot
parentd3a492c72f15ecf8debe56a3ee35eb213c9d9bcc (diff)
downloadupstream-f57806b56e5f6ca7bb9fb66d5b175b5f98ece93c.tar.gz
upstream-f57806b56e5f6ca7bb9fb66d5b175b5f98ece93c.tar.bz2
upstream-f57806b56e5f6ca7bb9fb66d5b175b5f98ece93c.zip
kernel: generic: Fix nftables inet table breakage
Commit b7265c59ab7d ("kernel: backport a series of netfilter cleanup patches to 4.14") added patch 302-netfilter-nf_tables_inet-don-t-use- multihook-infrast.patch. That patch switches the netfilter core in the kernel to use the new native NFPROTO_INET support. Unfortunately, the new native NFPROTO_INET support does not exist in 4.14 and was not backported along with this patchset. As such, nftables inet tables never see any traffic. As an example the following nft counter rule should increment for every packet coming into the box, but never will: nft add table inet foo nft add chain inet foo bar { type filter hook input priority 0\; } nft add rule inet foo bar counter This commit pulls in the required backport patches to add the new native NFPROTO_INET support, and thus restore nftables inet table functionality. Tested on Turris Omnia (mvebu) Fixes: b7265c59ab7d ("kernel: backport a series of netfilter cleanup ...") Signed-off-by: Brett Mastbergen <bmastbergen@untangle.com>
Diffstat (limited to 'package/boot')
0 files changed, 0 insertions, 0 deletions