Re: Socket send problem (ucLinux)


I noted that when i disrupt (eg 0.2sec ) the network connection the transfer
does not
resume.

If the Network connection is broken, neither of the sockets is informed that the connection is lost. Both think it's still working.

The one that some time later sends a packet does not receive an acknowledge packet from the addressees stack, so, after some 90 seconds it declares the connection broken and the application is informed. Still the other end thinks the connection is still working (though idle).

If (e.g.) the client application knows that the connection is broken, it might try a reconnect. If the cable is restored, the server will decline the connect, as it thinks there is still a working connection.

To improve this situation you need to implement a life check protocol lin the application or use the stack's "keep alive" feature.

-Michael
.

Relevant Pages

  • Re: peer to peer messaging
    ... attempts to open a connection to port 80 of the server at that IP address. ... For example a packet from my machine might have source IP ... Packets from the sever to my laptop would have those reversed. ...
    (comp.lang.java.programmer)
  • Re: IPFW Dynamic Rules
    ... > So if the dynamic rule has the same behaviour as the origination ... > rule on the same port with the same protocol, ... If client sends UDP query to DNS on your machine, you get the packet: ... is deleted after connection is inactive for some time. ...
    (FreeBSD-Security)
  • [NEWS] Cisco PIX TCP Connection DoS
    ... Get your security news from a reliable source. ... By crafting a special TCP packet and sending it to a vulnerable Cisco PIX, ... embryonic connection open until the embryonic connection timeout which is ...
    (Securiteam)
  • Re: Nmap questions concering my router
    ... that may have to be fetched) is downloaded as one connection. ... >> all addresses (and may listen using just one interface to receive all ... sends packets to the correct protocol driver ... wire to an IP packet, and hands this to the IP driver which strips off ...
    (comp.security.firewalls)
  • Re: Port "triggering"
    ... The reason you should specify the -d above is if you have two internal nets ... If you are connecting to some outside server your connection will never make ... Again, the rule you had takes every single packet going to port 3783, no ... At the end of each chain I do a: ...
    (comp.os.linux.security)