From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Matthew Donofrio" Subject: How exactly does RELATED work in Connection Tracking? Date: Mon, 21 Oct 2002 22:48:31 -0700 Sender: netfilter-admin@lists.netfilter.org Message-ID: <000801c2798e$a7dcfd70$09c809c0@PENT4> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C27953.FAFDD1E0" Return-path: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: To: netfilter@lists.netfilter.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C27953.FAFDD1E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone. Before I ask my question, I just want to alert everyone = that I am newbie to Linux and the netfilter architecture. OK, that = being said, here's my question. I'm trying to determine how exactly an = incoming packet is determined to be RELATED to an existing connection in = Connection Tracking. For instance, how exactly does a TCP connection = know that the packet is starting a new connection and this should be = deemed RELATED? What fields (for lack of a better word) are compared to = come to this conclusion? Thanks in advance. -Matt ------=_NextPart_000_0005_01C27953.FAFDD1E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everyone.  Before I ask my = question, I just=20 want to alert everyone that I am newbie to Linux and the = netfilter=20 architecture.  OK, that being said, here's my question.  I'm = trying to=20 determine how exactly an incoming packet is determined to be RELATED to = an=20 existing connection in Connection Tracking.  For instance, how = exactly=20 does a TCP connection know that the packet is starting a=20 new connection and this should be deemed RELATED?  What fields = (for=20 lack of a better word) are compared to come to this conclusion?  = Thanks in=20 advance.
 
-Matt
------=_NextPart_000_0005_01C27953.FAFDD1E0--