Re: Why are two hash tuples stored for each connection in the connection tracking system?

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

 



> You totally misunderstood me.
> All packets in both direction enter netfilter, and all packets leave
> netfilter unless they are discarded or queued.

Thanks for the example. It looks like my original intuition for what
the "original" and "reply" directions meant was correct (even though I
described it quite imprecisely).

This makes me still unclear on how conntrack figures out that the
original and reply packets are related. e.g. from the information in
the packet entering netfilter in the reply direction, how can it
determine that it is part of the same connection as the packet
entering netfilter in the original direction. I'll try and figure this
out and reply to this thread if I do.
--
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