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]

Subject: Re: Why are two hash tuples stored for each connection in the connection tracking system?
From: Will Sewell <me@xxxxxxxxxxxxxx>
Date: Fri, 6 Oct 2017 13:23:52 +0100
Cc: netfilter@xxxxxxxxxxxxxxx
In-reply-to: <5e618aa9-262a-b3b1-43e6-28fdcdfd1731@plouf.fr.eu.org>
References: <CAKMCqEL=UCUUn2=Ke7-4uJo-fij80k7u13zEOsHNh_AP_p2EKQ@mail.gmail.com> <0cc1bff1-b709-06ff-1dfa-5d4214397277@plouf.fr.eu.org> <6f1b85b3-4982-d14c-a7d0-9abca40489aa@plouf.fr.eu.org> <CAKMCqELnZLifhdEmbYEnPOX7SWAS4Y1L5KGBJ4YS_qT3QwkK=A@mail.gmail.com> <abe1f557-b3f7-1c41-ed15-5db7c7f5b1d0@plouf.fr.eu.org> <CAKMCqEJyaqmH5rnQGcmVYwxw=JxZYJd8gOHq-Wwuc375K+BuPw@mail.gmail.com> <62f03124-a3ed-1f17-3477-288c1f48c969@plouf.fr.eu.org> <CAKMCqEJLrtUEXo6xGHs2JMM3Z5dSg2wRfpi4bZNCf7yMtaOn5g@mail.gmail.com> <64d6734e-ca72-3788-42d4-afe495b3f372@plouf.fr.eu.org> <CAKMCqEJ4urXwNcwcQQ6y6_ogyhU7GDX_pQM=tusZOpHNvHoETQ@mail.gmail.com> <5e618aa9-262a-b3b1-43e6-28fdcdfd1731@plouf.fr.eu.org>

> There are variations for handling of "special" protocols such as ICMP which
> use header fields other than source/destination ports to identify
> connections.

Makes sense. Thanks again for your help!
--
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

References:
- Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Will Sewell
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Will Sewell
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Will Sewell
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Will Sewell
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Will Sewell
- Re: Why are two hash tuples stored for each connection in the connection tracking system?
  - From: Pascal Hambourg

Prev by Date: Why I can not use physdev module on iptables POSTROUTING chain?
Next by Date: Re: Why I can not use physdev module on iptables POSTROUTING chain?
Previous by thread: Re: Why are two hash tuples stored for each connection in the connection tracking system?
Next by thread: Re: Why are two hash tuples stored for each connection in the connection tracking system?
Index(es):
- Date
- Thread

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