[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] ETH_PAD_SIZE
From: |
Mumtaz Ahmad |
Subject: |
[lwip-users] ETH_PAD_SIZE |
Date: |
Thu, 14 Sep 2006 15:33:19 +0500 |
Hi all
I am using a ETH_PAD_SIZE=2 option but it seems that stack stop working with
that .I do see some areas where this is not taken care of and trying to
debug. Anyone who solved this problem,please comment.
----- Original Message -----
From: "Kieran Mansley" <address@hidden>
To: "Mailing list for lwIP users" <address@hidden>
Sent: Thursday, September 14, 2006 2:46 PM
Subject: Re: [lwip-users] TCP FIN question
> On Thu, 2006-09-14 at 15:10 +0530, Yadnesh Phadke wrote:
>
> > Why is this the case when, TCP documentation says that the client is
> > expected receive FIN from the server? Is the client always expected
> > to send RST to close connection from it's side? And FIN is used only
> > for closing connection initiated by the server?
>
> TCP connections are duplex, i.e. data can go in both directions, and
> each direction is closed independently. The FIN means "I've finished
> sending data in this direction", not "close the connection in both
> directions". The server will send a FIN when it has finished sending
> data (i.e. when the server application calls close()).
>
> If you really really must close a connection now and not care about any
> data getting lost, then you can use a RST, but it's not meant for normal
> closing of connections.
>
> Kieran
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>
> --
> This message has been scanned for viruses and
> dangerous content by Streaming Networks, and is
> believed to be clean.
--
This message has been scanned for viruses and
dangerous content by Streaming Networks, and is
believed to be clean.