Displaying 7 results from an estimated 7 matches for "in_public_deni".
Did you mean:
in_public_deny
2017 Dec 19
2
firewalld
I have two VMs, both with firewalld installed. One on machine It this in the IN_public chain:
Chain IN_public (2 references)
pkts bytes target prot opt in out source destination
81 3423 IN_public_log all -- * * 0.0.0.0/0 0.0.0.0/0
81 3423 IN_public_deny all -- * * 0.0.0.0/0 0.0.0.0/0
2017 Dec 19
0
firewalld
On Tue, 2017-12-19 at 15:05 -0800, Emmett Culley wrote:
> I have two VMs, both with firewalld installed. One on machine It
> this in the IN_public chain:
>
> Chain IN_public (2 references)
> pkts bytes target prot opt
> in out source destination
> 81 3423 IN_public_log all
> -- * * 0.0.0.0/0 0.0.0.0/0
2017 Dec 19
1
firewalld
On 12/19/2017 03:37 PM, Louis Lagendijk wrote:
> On Tue, 2017-12-19 at 15:05 -0800, Emmett Culley wrote:
>> I have two VMs, both with firewalld installed. One on machine It
>> this in the IN_public chain:
>>
>> Chain IN_public (2 references)
>> pkts bytes target prot opt
>> in out source destination
>> 81 3423
2017 May 28
1
Ovirt Hosted-Engine VM iptables
Hi
I would like to add rules into the iptables of the Hosted Engine VM in
Ovirt.
the version is oVirt Engine Version: 4.1.1.8-1.el7.centos
I have tried using the normal process for iptables (iptables-save etc),
but it seems that the file
/etc/sysconfig/iptables
this is ignored in the Ovirt Engine VM.
How can I add permanent rules into the Engine VM?
Kind regards
Andrew
2019 Jan 15
0
Cannot access other computers on LAN
ip_forward was not enabled, now it is. Still same result:
On VPN_office I use 'tcpdump -npi any icmp and host 192.168.1.1' and ping
192.168.1.1 from the client:
5:28:42.646203 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584, seq
1, length 64
15:28:43.663014 IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id 1584,
seq 2, length 64
15:28:44.688133 IP 172.16.0.3 >
2019 Jan 15
2
Cannot access other computers on LAN
Hello Julien,
Am Tue, 15 Jan 2019 09:30:23 +0100
schrieb Julien dupont <marcelvierzon at gmail.com>:
> In that case I see:
> IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq1, length 64
> IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq2, length 64
> IP 172.16.0.3 > 192.168.1.1: ICMP echo request, id2135, seq3, length 64
>
> Packet goes
2020 Jun 21
6
firewall questions
I'm running Centos 7.8.2003, with firewalld.
I was getting huge numbers of ssh attempts per day from a few specific
ip blocks.
The offenders are 45.0.0.0/24, 49.0.0.0/24, 51.0.0.0/24, 111.0.0.0/24
and 118.0.0.0/24, and they amounted to a multiple thousands of attempts
per day. I installed and configured fail2ban, but still saw a lot of
attempts in the logs, and the ipset created was