From owner-freebsd-net@FreeBSD.ORG Tue Jun 16 11:07:36 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B8B71065674 for ; Tue, 16 Jun 2009 11:07:36 +0000 (UTC) (envelope-from seesaravanan@yahoo.co.in) Received: from web8315.mail.in.yahoo.com (web8315.mail.in.yahoo.com [202.43.219.9]) by mx1.freebsd.org (Postfix) with SMTP id D5E8B8FC12 for ; Tue, 16 Jun 2009 11:07:34 +0000 (UTC) (envelope-from seesaravanan@yahoo.co.in) Received: (qmail 71924 invoked by uid 60001); 16 Jun 2009 11:07:33 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s1024; t=1245150452; bh=Rt/oBnBpAWBDWlUzdDJcGLLqfi1DnoiFPjizV6j+APc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=ycR8LcbTBm+4/KVDshmW0q6FZGQjWdfHiCyGiaINX6VNSpkzvohWQ5gradU18IRFxAS8n5s0ddkU9CYe0xznKipbIZIB+ssteSOjAL6Ki6567Sr0X6rtw4qyVeCTXa09+jGjtDhDZlQ3+Em2nAqu4NcIUBLXCOjig5p+GsSVAm0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=pHu0r9H3Wzkv4aILS3NZ3X5thLK+jXP1vdX/gXvm+eLu7KbrVqulKgF1NIahloGfqzCd5sKRE9rNM8UXq6/BdvTZCQL4TKaVGmifmVEIiX57JK5PGUlDmat6S9Z8LqNzUA58fnOgJk0IBXpwEJJ4Ml36iUhUEXls+J2JS+Pcbso=; Message-ID: <925929.71164.qm@web8315.mail.in.yahoo.com> X-YMail-OSG: iTpAFjoVM1m0fj93GEc_GUykBmKgqMBNNY2RHqvYwUKLEmqykxgZriT4HURHPZf_GKRom52bvsrQjC.r_y4ZVCOiMiLAxmY1T_1fJA5LTl6_5PhBgRv3QpLXpsNex8.aG7kAmcsUPYgw0EneWARXa.RD_fG0haOUUkhqAPCuL2Ao9z1gJV9q7oe7JPtHDAsHiLvSEVmNq5OWhYALggDitbw3OC98gjXesFIh3PxsmzQTRYWcSA-- Received: from [125.22.253.101] by web8315.mail.in.yahoo.com via HTTP; Tue, 16 Jun 2009 16:37:32 IST X-Mailer: YahooMailClassic/5.4.12 YahooMailWebService/0.7.289.15 Date: Tue, 16 Jun 2009 16:37:32 +0530 (IST) From: saravana perumal To: Louis Mamakos MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Mailer List Subject: Re: TCP Free-BSD setup behaviour. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2009 11:07:37 -0000 Hi=A0 Louie. =A0 As per Testing=20 =A0 1.Sending SYN and reaching the SYN_SENT state INTIALLY [Active open] 2. Then Expects to RECEIVE SYN packet and=20 3. To Send SYN & ACK=A0 to reach=A0 SYN-RCVD state. =A0 In Free BSD active SYN-RCVD state is not happening . =A0 In TCP state tranistion my expectation is represented for SYN_RCVD state. =A0 =A0 Thanks. Saravanan --- On Tue, 6/16/09, saravana perumal wrote: From: saravana perumal Subject: Re: TCP Free-BSD setup behaviour. To: "Louis Mamakos" Cc: "FreeBSD Mailer List" Date: Tuesday, June 16, 2009, 3:15 PM Hi Louie =A0 =A0We are trying to make Active Sync Received state. =A0 As per our testing we are trying to received Syn packet from APPLICATION en= d and to send syn & ACK from Device END and hence reaching the ACTIVE SYN-R= ECEIVED state. =A0 So initially make the application to send SYN sending the Initial SYN and o= nce Received the SYN packet , expecting the Device to Send SYN & ACK =A0 I hope the expectation should be rite in case of ACTIVE-SYN received State. =A0 Thanks. Saravanan =A0 --- On Tue, 6/16/09, Louis Mamakos wrote: From: Louis Mamakos Subject: Re: TCP Free-BSD setup behaviour. To: "saravana perumal" Cc: freebsd-net@freebsd.org, sarbalas@gmail.com Date: Tuesday, June 16, 2009, 3:05 AM On Jun 15, 2009, at 3:44 AM, saravana perumal wrote: > Hi Louie , >=20 >=20 > Thanks for the Response on my Queries. >=20 > For QUERY 3, > ACTIVE open frm Free BSD end: >=20 >=A0 =A0 =A0 =A0 FREE BSD=A0 =A0 =A0 =A0 =A0 APPLICATION >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0Send ---------> syn >=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0Receive <-------- SYN >=20 > Expect SYN & ACK-------------> Getting only ACK in this Scenario, >=20 >=A0 Now Expects FREE BSD to respond back with the SYN & ACK , but BSD is s= ending only ACK message as the response. There's no reason why the FreeBSD host would send another SYN; presumably t= he "APPLICATION" host received the SYN and responds back with SYN of it's o= wn and ACK of the FreeBSD host's SYN.=A0 Once the SYN has been ACK'd, there= 's no reason to resend it.=A0 I suppose I wonder why you expect the FreeBSD= system to retransmit it's SYN? > 4=A0 =A0 .When checking the State - TIME-WAIT=A0 =A0 Sending FIN and expe= cting the ACK ;Getting the ACK properly.=A0=A0=A0Sending Data Segment and E= xpecting the RST signal not getting the RST ; Instead DUT is sending the La= st TCP packet. Issue seen only in Free BSD >=20 >=20 > For this Issue mentioned above, Last TCP packet is jst a Testing packet w= ith the > following Field set=A0 in TIME-WAIT state , >=20 >=20 > TCP: ---- TCP Packet ---- > TCP: > TCP: Source Port=A0 =A0 =A0 =A0 =A0=A0=A0=3D 16815 (16815) > TCP: Destination Port=A0 =A0 =A0 =3D 16816 (16816) > TCP: Sequence Number=A0 =A0 =A0=A0=A0=3D 3865716731 (0xE66A27FB) > TCP: Acknowledgment Number =3D 0 (0x00000000) > TCP: Data Offset=A0 =A0 =A0 =A0 =A0=A0=A0=3D 5 (20 bytes) > TCP: Reserved=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D 0 > TCP: Control Bits=A0 =A0 =A0 =A0 =A0 =3D 0x10 > TCP:=A0 |543210 > TCP:=A0 |0.....=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D Urgent Pointer Isn't Signi= ficant > TCP:=A0 |.1....=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D Acknowledgment Is Signific= ant > TCP:=A0 |..0...=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D No Push Function > TCP:=A0 |...0..=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D No Reset Connection > TCP:=A0 |....0.=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D No Synchronize Sequence Nu= mbers > TCP:=A0 |.....0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D More Data From Sender > TCP: Window=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D 32752 bytes > TCP: Checksum=A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D 0x41A0 (Correct) > TCP: Urgent Pointer=A0 =A0 =A0 =A0 =3D 0 (Not Significant) > TCP: > TCP: --- Trailing Data [12 bytes] --- > TCP:=A0 53 61 6D 70 6C 65 20 44 61 74 61 00=A0 =A0 =A0 =A0 =A0 =A0 =A0=A0= =A0Sample Data. > TCP: --- Trailing Data End --- > From machine Sending=A0 to the FREE BSD machine, >=20 > This is to verify that Free BSD is in TIME-WAIT state. Not sure what good this packet trace is; the only reason the TCP would resp= ond with a RST segment is if the segment it receives is somehow bogus.=A0 P= erhaps that the send sequence is outside the window.=A0 If the data is with= in the window, it might be considered an "old" segment that happens to arri= ve, perhaps out-of-order; why would the local TCP reset the connection for = no good reason? louie =0A=0A=0A