From: Frank Carmickle <frank@carmickle.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Need help with netperf.bufferbloat.net server
Date: Sat, 30 Mar 2024 15:59:02 -0400 [thread overview]
Message-ID: <DF019B83-3BE8-4979-B320-8C55F99356DF@carmickle.com> (raw)
In-Reply-To: <A7795892-DB4A-4BF5-8298-D1FC3B5BCB13@gmail.com>
> On Mar 30, 2024, at 13:03, Rich Brown via Bloat <bloat@lists.bufferbloat.net> 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.
If you are looking to do some traffic steering, geodns is a great tool, if you are willing to either run your own authoritative DNS servers, or farm it out to a service that supports this, such as aws route53. I pretty busy right now, but I may have some time at some point to help spin up authoritative servers based on preferably knot, or pdns.
--FC
prev parent reply other threads:[~2024-03-30 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 17:03 Rich Brown
2024-03-30 18:12 ` Jonathan Foulkes
2024-10-07 12:56 ` Rich Brown
2024-03-30 19:59 ` Frank Carmickle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DF019B83-3BE8-4979-B320-8C55F99356DF@carmickle.com \
--to=frank@carmickle.com \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox