[Top][All Lists]

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

SV: [lwip-users] TCP connect problem

From: Jan Wester
Subject: SV: [lwip-users] TCP connect problem
Date: Thu, 24 Feb 2005 18:14:13 +0100

I have tryed the patch I send to you, and now it response with RST, and try
with new SYN,
but the other side sometimes still answere with ACK, so maybe something have
to change where too.

Jan Wester
Scheelegatan 11
SE-112 28 Stockholm
+46 8 449 05 30

-----Ursprungligt meddelande-----
Från: address@hidden
[mailto:address@hidden För Adam Dunkels
Skickat: den 24 februari 2005 15:52
Till: address@hidden; Mailing list for lwIP users
Ämne: Re: [lwip-users] TCP connect problem

On Thu, 2005-02-24 at 14:23 +0000, Kieran Mansley wrote:
> On Thu, 2005-02-24 at 15:19 +0100, Jan Wester wrote:
> > Hi
> > Normaly I can do many TCP connect-close sequence, but if I restart 
> > my system and try to do TCP connect I often got tcp_error.
> > Is it any problem with seq no ? I using 0.7.2 On the sniffer I can 
> > see SYN SEQ=6525
> >         ACK=6533        Only ack ?
> > And after lot of try it connect
> > SYN SEQ=6595
> > SYN ACK=6596        Connect
> Sounds like one of the machines is interpreting the SYN as relating to 
> a connection that existed before the reboot.  As it thinks it's 
> already open, it responds with an ACK rather than a SYN-ACK, although 
> I'm not sure this is correct behaviour: I'd have to check the RFC to be
> Eventually, the connection times out and then the SYN succeeds.  

If I remember correctly, yhis is the intended behavior according to the RFC,
but with a small addition: the ACK should trigger an RST from the side that
sent the SYN. This will abort the connection. (But I'm not sure that lwIP
follows the RFC in this case.)


Adam Dunkels, Swedish Institute of Computer Science
http://www.sics.se/~adam/, <address@hidden>

lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]