On 6/26/2019 2:41 AM, MRob wrote:
> I am working to a CentOS 6 server with nonstandard iptables system without
> rule for
> ACCEPT ESTABLISHED connections. All tables and chains empty (flush by legacy
> custom
> script) so only filter/INPUT chain has rules (also fail2ban chain):
>
> Chain INPUT (
On 6/25/19 11:41 PM, MRob wrote:
When fail2ban block a IP address, established connections are allowed
to continue, but with no rule to accept established connections how is
that possible?
It doesn't look like it would be.
1: Open a connection that will demonstrate the problem later.
2: Trig
On 6/26/19 8:41 AM, MRob wrote:
I am working to a CentOS 6 server with nonstandard iptables system without rule
for ACCEPT ESTABLISHED connections. All tables and chains empty (flush by
legacy custom script) so only filter/INPUT chain has rules (also fail2ban
chain):
Chain INPUT (policy ACCEP
On 2019-06-26 02:41, MRob wrote:
I am working to a CentOS 6 server with nonstandard iptables system
without rule for ACCEPT ESTABLISHED connections. All tables and chains
empty (flush by legacy custom script) so only filter/INPUT chain has
rules (also fail2ban chain):
Chain INPUT (policy ACCEPT)
I am working to a CentOS 6 server with nonstandard iptables system
without rule for ACCEPT ESTABLISHED connections. All tables and chains
empty (flush by legacy custom script) so only filter/INPUT chain has
rules (also fail2ban chain):
Chain INPUT (policy ACCEPT)
target prot opt source
5 matches
Mail list logo
