On Fri, 2017-09-22 at 08:38 -0700, Gordon Messmer wrote:
> On 09/21/2017 11:30 PM, Cristian Sava wrote:
> > Why do I need to specify this long list of parameters for basic
> > things?
>
>
> If you're doing this for virtualization purposes (as opposed to
> creating
> a network bridge with multipl
Looks like your ipset wasn't created or something caused it to be deleted.
ipset v6.29: The set with the given name does not exist
Do you find the named ipset with: ipset -L -n
Also, your default action (firewallcmd-allports.conf) doesn't use ipset. Somehow
your jail is using firewallcmd-ipset.c
On 24/09/17 15:10, Samuel Sieb wrote:
On 09/23/2017 10:22 PM, Stephen Davies wrote:
On 05/03/17 12:28, Stephen Davies wrote:
It looks as if the automatic start may be happening too early in the boot
process.
I think this is your answer.
Same issue with F25.
The OpenVPN log says:
TCP/UDP:
David,
Is this still broken? I'd like to trade some debugging attention for a primer
on setting up IPSec, which i've never gotten around to.
On 11Aug2017 14:12, David A. De Graaf wrote:
I use an ipsec tunnel to connect my LAN (192.168.2.h) in North
Carolina to my son's LAN (192.168.1.h) in M
I'm trying to configure fail2ban and it appears as if it is correctly
identifying addresses to ban however it doesn't appear to be successful
in banning hosts:
2017-09-24 16:01:46,073 fail2ban.actions [3591]: NOTICE [sshd]
Ban 91.210.178.96
2017-09-24 16:01:46,494 fail2ban.action
