Displaying 4 results from an estimated 4 matches for "snapshot20161117".
2017 Jan 12
0
[Bug 1111] New: extensions: libxt_hashlimit: fix print_rate.
...d=490&action=edit
use uint64 modifier to print rate
This fixes iptables outputs 10/(null) instead of 10/sec as upto limit.
xt_hashlimit is already tagged C99.
A side effect is to get back openvpnas hooks when hashlimit upto is used.
This was tested (both breakage and fix) with iptables 1.6.0+snapshot20161117
from debian sid and testing.
NB: there are other similar printf placeholders that would benefit from the
same fix in libxt_hashlimit, but they are less critical (error reporting).
I am also uneasy with print_rate period parameter as uint32, I believe it
should have switched to uint64 with revisio...
2019 Feb 06
1
Samba and UFW
Louis,
Last lines in /etc/default/ufw:
IPT_MODULES="nf_conntrack_ftp nf_nat_ftp nf_conntrack_irc nf_nat_irc
nf_conntrack_netbios_ns"
Looks like nf_contrack_netbios_ns is already loaded.
iptables -S requires more arguments. Suggestions?
Marty
2019 Nov 11
13
[Bug 1381] New: Conntrackd segfaults when committing external caches
...not segfault every time. Sometimes it takes 5-10 iterations starting
and stopping the keepalived daemon which will invoke conntrackd to flush the
caches and subsequently segfault.
Kernel: 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
Conntrackd: 1.4.4+snapshot20161117
--
You are receiving this mail because:
You are watching all bug changes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.netfilter.org/pipermail/netfilter-buglog/attachments/20191111/6471ebbc/attachment.html>
2018 Dec 04
3
Samba and firewalling
Hai,
Just a questions, this might be a bug, might not, but for this one i need some help.
Setup, debian 9.
Member server samba 4.9.3
AD DC servers samba 4.8.7
Im setting up the member with a very tight firewall, so nothing in/our/routed unless its defined.
Im using UFW firewall for it.
I notice the following in my member its firewall logs, and this only happend when i run : id or