#147 No timeout with TCP if destination is not reachable

[Michael Anderegg]

If TCP is used for sending MD and the destination is not reachable, no timeout is raised.

[Bernd Löhr]

Hi Michael,

what is the exact situation:
a) Destination is offline -> there is an immediate error response from the stack (see attached picture)
b) Destination is online, but no TCP listener (TCP port 17225 not bound) -> there will be a reply timeout error
c) same as b) but MD Listener (Application) does not reply in time -> there will be a reply timeout error

[Michael Anderegg]

Hi Bernd,
The situation is part a), but is has already been fixed with the issue [#148].
Joachim and I working for the same company. He is developer and I’m tester. There was a misunderstanding so Joachim put a issue on developer view while I add the issue as tester.

[mike]

closed as duplicate of [#148]