Hi,
just a follow up from today.
On host, where I was debuging firehol behaviour on iptables-nft vs. iptables-
legacy (before reporting bug) , I got strange behavior after upgrading to
3.1.6+ds-8.
It was caused by my manual change of iptables alternatives -legacy one.
Sequence was like this:
in
Hello, thanks for your reports and the patch.
On 10/04/2019 21:29, Libor Klepáč wrote:
> Hi,
> usage of -legacy variant can be patched in during build time.
Indeed. But the question is rather why we should favour the legacy version over
the default one.
>
> Included patch tested by manual runn
Hello, thanks for your report.
On 10/04/2019 13:10, Libor Klepáč wrote:
> Package: firehol
> Version: 3.1.6+ds-7
> Severity: wishlist
>
> Hi,
> firehol seems to have problem to reread rules in nofast mode when using
> iptables-nft.
> See: https://github.com/firehol/firehol/issues/352
>
> Here i
Hi,
usage of -legacy variant can be patched in during build time.
Included patch tested by manual running (i don't have disk space to install
tex) of:
./autogen.sh && ./configure && make
and checking generated ./sbin/install.config
Libor
Description: compatibility with iptables-legacy
Author
Package: firehol
Version: 3.1.6+ds-7
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
firehol seems to have problem to reread rules in nofast mode when using
iptables-nft.
See: https://github.com/firehol/firehol/issues/352
Here is part of output, it goes on to ERROR : # 30
5 matches
Mail list logo
