From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from sender4-pp-f112.zoho.com (sender4-pp-f112.zoho.com [136.143.188.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 3635A3B2A4 for ; Sat, 30 Mar 2024 14:12:38 -0400 (EDT) ARC-Seal: i=1; a=rsa-sha256; t=1711822357; cv=none; d=zohomail.com; s=zohoarc; b=Y1eAbaq9GkwJgXhbgxmRHb6sSvmXKnS4MkXGPfGT4T5A9GRsSEB9Rpwwge21wx322TQ1XnCAQav4CPQ0kDLmKixGEb+jRZ3oFxjYtC8AdfdAQFbTy1O472lDxX5oKl+PZ/wMRCo3yJBNM+xJAAOD96WLc88yPe0Ykqjr33cEDes= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1711822357; h=Content-Type:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=Mt6mZNmM0V32ITPD1tb0qgFHYgaypwZdTVQLd0shdD8=; b=BNBqSdg+htLLIDPYJeBiAyW7FtZENdGhyGwmQFXg2zpSEIjM1fbfnmbff+lI6AqwkOTI+MwcCNw9dyubRb1UM6SszRcSU+oCXf2+AmWabZU+z0fVAkf7YhbXonlqIhlldmU9c3uik5LIH8T3IGx8N4ppn/53KQgMir+WozgOj4Y= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=jonathanfoulkes.com; spf=pass smtp.mailfrom=jf@jonathanfoulkes.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1711822357; s=zoho; d=jonathanfoulkes.com; i=jf@jonathanfoulkes.com; h=Date:Date:From:From:To:To:Cc:Cc:Message-Id:Message-Id:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Reply-To; bh=Mt6mZNmM0V32ITPD1tb0qgFHYgaypwZdTVQLd0shdD8=; b=b/1BGY6dgoPPkeL3IlKCx4Qb/vNWtlSKgfqAo7IojohkVgKCpKSY97+rCk9faR9z anbfZCu6I791VApay7TaTafF/Ny1+CPBn4Ey7EAvbYbYOvz1DIDLKREpFR454slOqDV /ySqKOHJj0F5Ip98cmKxmhjyKxQ008tLY/4QOdF4= Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1711822354613112.60028263947197; Sat, 30 Mar 2024 11:12:34 -0700 (PDT) Date: Sat, 30 Mar 2024 14:12:34 -0400 From: Jonathan Foulkes To: "Rich Brown" Cc: "Rich Brown via Bloat" Message-Id: <18e90903899.c3a2cea42205429.4572523016718960380@jonathanfoulkes.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7120273_588090483.1711822354585" Importance: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail Subject: Re: [Bloat] Need help with netperf.bufferbloat.net server X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Mar 2024 18:12:38 -0000 ------=_Part_7120273_588090483.1711822354585 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Hi Rich, 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. 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. Use different passwords for each server to have fine-grained access controls. I hope that helps, Jonathan Foulkes ---- On Sat, 30 Mar 2024 13:03:00 -0400 Rich Brown via Bloat wrote --- Hi folks, This note was prompted by a question from the crusader github repo [1] where I wrote the following: >> It seems to me that the server netperf.bufferbloat.net (also called netperf-east.bufferbloat.net) has been down for quite a while. > > Yes. I have been stymied by heavy abuse of the server. In addition to legitimate researchers or occasional users, > I see people running a speed test every five minutes, 24x7. > > I created a bunch of scripts [2] to review the netperf server logs and use iptables to shut off people who abuse the server. > Even with those scripts running, I have been unable to keep the traffic sent/received below the 4TB/month cap at my VPS. Does anyone have thoughts about how to continue providing a netperf server at the name "netperf.bufferbloat.net" while not overwhelming any particular server? Many thanks. Rich [1] https://github.com/Zoxc/crusader/issues/14#issuecomment-2028273112 [2] https://github.com/richb-hanover/netperfclean _______________________________________________ Bloat mailing list mailto:Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat ------=_Part_7120273_588090483.1711822354585 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
Hi Rich,

Sure, here's= what we did to protect our Netperf servers: Require a password to run netp= erf (it's a command line parameter on the client), and rotate the password = regularly.

This means users will need to sign = up for access, and get an email every time the password is rotated. That wa= y you know who is using (or abusing) the services. If it is being abused, k= nock out the abuser from the list, and rotate the pwd.

Use different passwords for each server to have fine-grained acces= s controls.

I hope that helps,

Jonathan Foulkes

---- On Sat, 30 Mar 2024 13:03:00 -0400 = Rich Brown via Bloat <bloat@lists.bufferbloat.net> wrote ---
<= /div>

Hi folks,

This note was prompted by a question from the cru= sader github repo [1] where I wrote the following:

>> It seems= to me that the server netperf.bufferbloat.net (also called netperf-east.bu= fferbloat.net) has been down for quite a while.
>
> Yes. I have= been stymied by heavy abuse of the server. In addition to legitimate resea= rchers or occasional users,
> I see people running a speed test every= five minutes, 24x7.
>
> I created a bunch of scripts [2] to re= view the netperf server logs and use iptables to shut off people who abuse = the server.
> Even with those scripts running, I have been unable to = keep the traffic sent/received below the 4TB/month cap at my VPS.

Do= es anyone have thoughts about how to continue providing a netperf server at= the name "netperf.bufferbloat.net" while not overwhelming any particular s= erver? Many thanks.

Rich

[1] https://gi= thub.com/Zoxc/crusader/issues/14#issuecomment-2028273112
[2] https:= //github.com/richb-hanover/netperfclean
____________________________= ___________________
Bloat mailing list
Bloat@lists.bufferbloat.net
https= ://lists.bufferbloat.net/listinfo/bloat

------=_Part_7120273_588090483.1711822354585--