Date: Tue, 12 Aug 2014 16:04:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 192599] zero window and persist timer not set Message-ID: <bug-192599-8-fFnftKjeT0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192599-8@https.bugs.freebsd.org/bugzilla/> References: <bug-192599-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192599 --- Comment #2 from Jeremiah <jlott@averesystems.com> --- Created attachment 145717 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145717&action=edit recv.py I was asked to share my test programs, so I will. However, I'm not sure that it will help reproduce it in another environment. It was very dependent on network timing as well as the features of the network drivers on both side (do they support tso/lro, etc.). I tweaked it endlessly until I got something that reproduced it somewhat consistently in our environment. The names of the files are probably a bit of a misnomer, too (backwards from what you would expect). Run recv.py on the box you want to reproduce the problem on and send.py on another freebsd box. It does not work running on same box, since MTU gets set to 16K in that case. You can only tell if the problem is reproduced by running a packet trace during the run and seeing if there are zero window probes sent or not. You'll have to SIGINT both programs after checking the packet trace, they just wait in the zero window condition forever whether the probes are sent or not. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192599-8-fFnftKjeT0>