Networking Forums

Networking Forums > Computer Networking > Linux Networking > Unexpected behaviour of TCP...

Reply
Thread Tools Display Modes

Unexpected behaviour of TCP...

 
 
srinivasan.gct@gmail.com
Guest
Posts: n/a

 
      10-07-2005, 02:07 PM
hi,
I implemented the Echo server& client program...After establishing
the connection i will send the data from client then it will be echoed
to client again....
But.. when i am terminate the server process (by pressing CTRL+c),
the state transsions occured...that is server process in FIN_WAIT2 and
client in CLOSE_WAIT state..

After some time the netstat command only shows the transistion state
of the client as CLOSE_WAIT .. the server closed its connection... Why?

after this happened, it is possible to send the data from client to
server only one time but for next try it shows the "broken pipe" error
message... Why?

Is there any relationship between FIN_WAIT2 state and the timer?

thanks & regards
sri

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slow speed - unexpected cause allan Broadband 0 08-26-2007 10:23 AM
Unexpected behavior by 'tc' Naren Linux Networking 0 08-07-2007 11:57 PM
Linux TCP - unexpected retransmissions Francois Linux Networking 9 05-30-2007 05:27 PM
unexpected deauthentication David Boyer Wireless Internet 0 08-05-2005 09:57 PM
Unexpected Shutdown Myrt Webb Wireless Networks 2 11-10-2004 01:02 AM



1 2 3 4 5 6 7 8 9 10 11