On 08/10/2014 12:23, John-Mark Gurney wrote:
[..]
The next thing would be to get a tcpdump, and take a look at the
window size.. Wireshark has lots of neat tools to make this analysis
easy... Another tool that is good is tcptrace.. It can output a
variety of different graphs that will help you track down, and see
what part of the system is the problem...
Also, SIFTR (man siftr) can provide detailed insight into the TCP flow's state
over time.
cheers,
gja
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
