<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I finally got around to implementing Jonathan Foulkes' suggestion and set up the `netserver` at <a href="http://netperf.bufferbloat.net" class="">netperf.bufferbloat.net</a> to require a passphrase - `netserver -Z passphrase`<div class=""><br class=""></div><div class="">I have set up a daily passphrase change - people can get the current day's value at <a href="http://netperf.bufferbloat.net" class="">netperf.bufferbloat.net</a>. I have a cron job that runs at 00:01 to kill all the `netserver` processes, regenerate a passphrase, and restart with the new passphrase. The web server substitutes that passphrase into the web page, so people can get a fresh copy every day. You can see the machinery at my repo: <a href="https://github.com/richb-hanover/Netperf-with-passphrase" class="">https://github.com/richb-hanover/Netperf-with-passphrase</a></div><div class=""><br class=""></div><div class="">I also updated the `betterspeedtest.sh` script to pass through a `-Z passphrase` option if it's specified. See </div><div class=""><a href="https://github.com/richb-hanover/OpenWrtScripts/blob/master/betterspeedtest.sh" class="">https://github.com/richb-hanover/OpenWrtScripts/blob/master/betterspeedtest.sh</a></div><div class=""><br class=""></div><div class="">Hopefully, this will eliminate the problem I was having: blowing through my VPS traffic limit (4TBytes) in the first few days of the month... (It'll also be interesting to see how many people retrieve the passphrase each day...)</div><div class=""><br class=""></div><div class="">Comments and field reports (positive and negative) welcomed. Thanks</div><div class=""><br class=""></div><div class="">Rich<br class=""><div><br class=""></div><div>PS I wonder if it adding a `-Z` option to flent or other netperf cients would be useful</div><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 30, 2024, at 2:12 PM, Jonathan Foulkes <<a href="mailto:jf@jonathanfoulkes.com" class="">jf@jonathanfoulkes.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta content="text/html;charset=UTF-8" http-equiv="Content-Type" class=""><div class=""><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;" class=""><div class="">Hi Rich,<br class=""></div><div class=""><br class=""></div><div class="">Sure, here's what we did to protect our Netperf servers: Require a password to run netperf (it's a command line parameter on the client), and rotate the password regularly.<br class=""></div><div class=""><br class=""></div><div class="">This means users will need to sign up for access, and get an email every time the password is rotated. That way you know who is using (or abusing) the services. If it is being abused, knock out the abuser from the list, and rotate the pwd.<br class=""></div><div class=""><br class=""></div><div class="">Use different passwords for each server to have fine-grained access controls.</div><div class=""><br class=""></div><div class="">I hope that helps,</div><div class=""><br class=""></div><div id="Zm-_Id_-Sgn" data-sigid="8168650000000048003" data-zbluepencil-ignore="true" class=""><div class="">Jonathan Foulkes<br class=""></div></div><div class=""><br class=""></div><div class="zmail_extra_hr" style="border-top: 1px solid rgb(204, 204, 204); height: 0px; margin-top: 10px; margin-bottom: 10px; line-height: 0px;"><br class=""></div><div class="zmail_extra" data-zbluepencil-ignore="true"><div class=""><br class=""></div><div id="Zm-_Id_-Sgn1" class="">---- On Sat, 30 Mar 2024 13:03:00 -0400 <b class="">Rich Brown via Bloat <<a href="mailto:bloat@lists.bufferbloat.net" class="">bloat@lists.bufferbloat.net</a>></b> wrote ---<br class=""></div><div class=""><br class=""></div><blockquote id="blockquote_zmail" style="margin: 0px;" class=""><div class="">Hi folks,<br class=""><br class="">This note was prompted by a question from the crusader github repo [1] where I wrote the following:<br class=""><br class="">>> It seems to me that the server <a href="http://netperf.bufferbloat.net" class="">netperf.bufferbloat.net</a> (also called <a href="http://netperf-east.bufferbloat.net" class="">netperf-east.bufferbloat.net</a>) has been down for quite a while.<br class="">><br class="">> Yes. I have been stymied by heavy abuse of the server. In addition to legitimate researchers or occasional users,<br class="">> I see people running a speed test every five minutes, 24x7.<br class="">><br class="">> I created a bunch of scripts [2] to review the netperf server logs and use iptables to shut off people who abuse the server.<br class="">> Even with those scripts running, I have been unable to keep the traffic sent/received below the 4TB/month cap at my VPS.<br class=""><br class="">Does anyone have thoughts about how to continue providing a netperf server at the name "<a href="http://netperf.bufferbloat.net" class="">netperf.bufferbloat.net</a>" while not overwhelming any particular server? Many thanks.<br class=""><br class="">Rich<br class=""><br class="">[1] <a href="https://github.com/Zoxc/crusader/issues/14#issuecomment-2028273112" target="_blank" class="">https://github.com/Zoxc/crusader/issues/14#issuecomment-2028273112</a><br class="">[2] <a href="https://github.com/richb-hanover/netperfclean" target="_blank" class="">https://github.com/richb-hanover/netperfclean</a><br class="">_______________________________________________<br class="">Bloat mailing list<br class=""><a href="mailto:Bloat@lists.bufferbloat.net" target="_blank" class="">Bloat@lists.bufferbloat.net</a><br class=""><a href="https://lists.bufferbloat.net/listinfo/bloat" target="_blank" class="">https://lists.bufferbloat.net/listinfo/bloat</a><br class=""></div></blockquote></div></div><br class=""></div></div></blockquote></div><br class=""></div></div></body></html>