Re: Synflood filtering and Conntrack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jozsef Kadlecsik a écrit :
> 
> I don't see why it looks soo complicated: of course, a ct entry is created 
> by conntrack whenever a new connection is detected. And of course the 
> entry is destroyed if the packet, which triggered to create the new entry,
> is dropped by a rule. Why should the conntrack entry be kept, if the 
> connection is not allowed by the rules?
> 
> The new ct entries are kept in the unconfirmed list and only added to the 
> conntrack hash iff the entry will be confirmed, that is the entry-creating 
> packet won't be dropped by a rule.

Thanks for this explanation. Just one more clarification, please : is
the conntrack entry destroyed also if the packet which triggered its
creation is dropped by something else than an iptables rule, such as
routing decision, TTL exceeded, conflict with an existing NAT mapping ?


--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux