Socket send problem (ucLinux)

Hi

I have a problem with sockets:(Coldfire DilnetPC DNP5280)

I have a listen socket that can send data to a remote client.
If a client connects, the server socket opens a file and sent its bytes to
the socket so the remote client can process the bytes.

I noted that when i disrupt (eg 0.2sec ) the network connection the transfer
does not
resume. The same happens when using a slow connection.(e.g. with a gateway
through internet)

The program seems to block on the send() function.
The full sendbuffer seems to block the send() becorse the data can't be
delivered but it should resume as ethernet communication proceeds.

I would expect get a return value of -1 when the network disruption takes
too long (causing a sent timeout) but this is not the case.

When i do this experiment between two windows machines i don't get this
problem. (transfer resumes a few moments i reconnect the network ) neither
does it occur between 2 linux desktop machines.

Is there a problem with the TCPIP stack in ucLinux ? or with the low level
network driver ?

any help much appreciated.

Johan.


.

Relevant Pages

  • [PATCH 1/1] IPN: Inter Process Networking
    ... +IPN is an Inter Process Communication service. ... +interface and protocols used for networking. ... +to a "network". ... +creates a communication socket. ...
    (Linux-Kernel)
  • Re: [PATCH 1/1] IPN: Inter Process Networking
    ... +IPN is an Inter Process Communication service. ... +interface and protocols used for networking. ... +to a "network". ... +creates a communication socket. ...
    (Linux-Kernel)
  • Re: Home Networking
    ... has 4 network sockets) in the roofspace and then wire a CAT5 network ... NTE5 master socket, so I don't need a filter at each phone outlet. ... A number of different suppliers offer such equipment, including Solwise whose range I use including their Homeplug ADSL Modem Router. ...
    (uk.telecom.broadband)
  • Re: multithreaded dialog application
    ... multiple threads, a rewrite of the piece of crap in the MSDN. ... the socket messages are posted to the main thread to be processed. ... Nearly all the socket messages are simply passed on to a child dialog ... If you have only one network interface then there ...
    (microsoft.public.vc.mfc)
  • Network freezes up
    ... PROBLEM: Network freezes up. ... Client side machine ok. ... Reboot the server machine cures the problem for a while. ... socket classes, not based on MFC. ...
    (microsoft.public.win32.programmer.networks)
Quantcast