perhaps I am running an older verison of iptables (1.4.7)? I don't show that flag at all.
Solution was to modify actions.d/iptables-common.local and put int [Init] lockingopt= That got rid of the flag and iptables started properly. Now to figure out why my jails got clobbered. Time to start from scratch. On 2015-10-20 03:58 PM, Kenneth Porter wrote: > On 10/20/2015 2:20 PM, Richard Nairn wrote: >> I am getting an error starting up iptables now. It seems to be running >> iptables with a bad flag "-w": > No solution, but I was unaware of the -w flag. I found it got added in > 2013 to deal with parallel invocations of iptables trampling each other: > > http://git.netfilter.org/iptables/commit/?id=93587a04d0f2511e108bbc4d87a8b9d28a5c5dd8 > > The optional time delay argument to -w was added in 2014: > > http://www.spinics.net/lists/netfilter-devel/msg31949.html > > ------------------------------------------------------------------------------ > _______________________________________________ > Fail2ban-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/fail2ban-users ------------------------------------------------------------------------------ _______________________________________________ Fail2ban-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fail2ban-users
