Otherwise, netcat can be very useful, and as another noted, iperf. If it's really just random packet loss, some of the lesser-used options of ping at one end and tcpdump/whatever at the other will often do it. 'All those of a certain size?' is especially common. But almost always it's best to make a guess about what kinds of packets are getting lost. Yes, for two hosts communicating and you suspect packet loss, wireshark/tshark/tcpdump is the right tool ideally capture on both server and client, then you actually see the lost packet on one but not the other.

Details of which depend on exactly what phase of connection the sockets are timing out. Sockets timing out on loopback is much more likely to be a programming error.

Just standard TCP sockets.'įor TCP connections over loopback, packet loss is exceptionally rare except under massive overload, and depends on the OS. best regards Relevant answer Edmund Greaves Answer Wireshark has an option under Analyze -> Expert Information that shows a summary of packet loss 'Previous segments (s) not. 'I have an application that spawns processes that communicate with each other through TCP using the loopback interface on the same host.

Wireshark captures find in packet