<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Toke,<div><br><div><div>On Jan 19, 2014, at 21:58 , Toke Høiland-Jørgensen <<a href="mailto:toke@toke.dk">toke@toke.dk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Sebastian Moeller <<a href="mailto:moeller0@gmx.de">moeller0@gmx.de</a>> writes:<br><br><blockquote type="cite">I noticed the new "hostnames are mandatory police" kick in:<br></blockquote><br>Right, botched that; should be fixed properly now.<br></blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>That was fast, and:</div><div>bash-3.2$ ./netperf-wrapper --list-tests<br>Available tests:<br> cisco_5tcpup : RTT Fair Realtime Response Under Load<br> cisco_5tcpup_2udpflood : Cisco 5TCP up + 2 6Mbit UDP<br> cubic_ledbat_1 : Cubic vs LEDBAT upload streams w/ping<br> ledbat_cubic_1 : Cubic vs LEDBAT upload streams w/ping<br> ping : Straight ping test<br> reno_cubic_westwood_ledbat : Realtime Response Under Load<br> (with different congestion control algs)<br> reno_cubic_westwood_lp : Realtime Response Under Load<br> (with different congestion control algs)<br> rrul : Realtime Response Under Load<br> rrul46 : Realtime Response Under Load - Mixed IPv4/6<br> rrul46compete : Realtime Response Under Load - Mixed v4/v6 compete<br> rrul_be : Realtime Response Under Load - exclusively Best Effort<br> rrul_noclassification : Realtime Response Under Load - no classification on data flows<br> rtt_fair : RTT Fair Realtime Response Under Load<br> rtt_fair4be : RTT Fair Realtime Response Under Load<br> rtt_fair6be : RTT Fair Realtime Response Under Load<br> tcp_1down : Bidirectional TCP streams w/ping<br> tcp_1up : Single TCP upload stream w/ping<br> tcp_bidirectional : Bidirectional TCP streams w/ping<br> tcp_download : TCP download stream w/ping<br> tcp_upload : TCP upload stream w/ping<br> udp_flood : UDP flood w/ping<br>bash-3.2$ <br><br></div><div>Thanks a lot.</div><br><blockquote type="cite"><br><blockquote type="cite">Wireless is weird...<br></blockquote><br>Yes, wayy too much black magic involved…</blockquote><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>What I failed to mention, testing against demo (~32ms unloaded ping RTT) from home gives ping RTT around 50ms, from the university 200ms (both with tcp_bidirectional). Ouch, and this with a massive rsync job running at home on a wired machine(over the atlantic, so sharing resources with tcp_bidirectional). </div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Dave, you are right default wireless performance truly is suboptimal…</div><div><br></div><div>best</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>Sebastian</div><div><br></div><div><img height="240" width="320" apple-width="yes" apple-height="yes" id="b06565d2-bf47-4879-9299-f50903464bd1" src="cid:CDB1EB13-042B-4379-8AD8-6E1FBD1594FD@home.lan"></div><div><img height="240" width="320" apple-width="yes" apple-height="yes" id="e39437fc-bc21-4571-8d88-2ee82d2267cb" src="cid:B865FC1E-18BF-405D-8110-6372E4A11B02@home.lan"></div><br><blockquote type="cite"><br>-Toke<br></blockquote></div><br></div></body></html>