I found it nearly impossible to make a sensible universal default
setting, since there are two conflicting scenarios, deny all and
accept all.
I'm closing all bugs related to startup/cleanup scripts, and
encouraging users to edit every script under /etc/miniupnpd/ before
using miniupnpd, rather th
Package: miniupnpd-nftables
Version: 2.3.7-1
Followup-For: Bug #1066874
Of course I realise seconds later the actually reason why miniupnpd rules
need living in the same hook as the main firewall (namely, traffic accepted
in a miniupnpd table can still get dropped by the same hook in a different
Package: miniupnpd-nftables
Version: 2.3.7-1
Followup-For: Bug #1066874
Hello,
I now present for consideration my modified versions of nft_init.sh,
nft_removeall.sh, and miniupnpd_functions.sh. It hopes to resolve #1066874
(and #1090753) by allowing users to nominate a different table to use in
Package: miniupnpd-nftables
Version: 2.3.4-1
Severity: important
Dear Maintainer,
I've changed my system to use nftables for firewall rules and found out that
miniupnpd-nftables
clobbered everything else on FORWARD.
(specifically, docker containers)
Looking at all the rules and nft_init.sh, it
4 matches
Mail list logo
