From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: Network chatter generator
Date: Sun, 25 Feb 2024 11:12:25 -0500 [thread overview]
Message-ID: <CAA93jw6E0n0ZNMj2BnOFWHv1GPAcz6zCC1VR6b6Cj-TTq6+rDg@mail.gmail.com> (raw)
In-Reply-To: <65d9fa7c.170a0220.556d0.d465SMTPIN_ADDED_MISSING@mx.google.com>
---------- Forwarded message ---------
From: G <lists@1337.io>
Date: Sun, Feb 25, 2024 at 11:09 AM
Subject: Re: Network chatter generator
To: <nanog@nanog.org>
Here's some tools that I've used to stress test gear over the years. You
may or may not find some of them useful for your use case:
(1) T50 - be *really* careful with this one:
- Source: https://gitlab.com/fredericopissarra/t50
(2) Yersina (can be used for DHCP stress testing)
- Source: https://github.com/tomac/yersinia
- Useful info for DHCP-specific stress testing:
https://www.amirootyet.com/post/dhcp-dos-attack-with-yersinia-in-kali/
(3) wrk - L7 endpoint load testing - I typically use an Ansible playbook
to generate artificial load from multiple source systems, which also
allows you to consolidate the stdout reporting from each system
- Source: https://github.com/wg/wrk
--
-G
On 2024-02-23 17:33, Brandon Martin wrote:
> Before I go to the trouble of making one myself, does anybody happen to
> know of a pre-canned program to generate realistic and scalable amounts
> of broadcast/broad-multicast network background "chatter" seen on
> typical consumer and business networks? This would be things like lots
> of ARP traffic to/from various sources/destinations within a subnet,
> SSDP, MDNS-SD, SMB browser traffic, DHCP requests, etc.?
>
> Ideally, said tool would have knobs to control the amount of traffic
> and whether a given type of traffic is present.
>
> This is mostly for torture testing "IoT" type devices by exposing them
> to lots of diverse, essentially nonsense traffic that they're likely to
> see in a real environment.
>
> --
> Brandon Martin
--
https://blog.cerowrt.org/post/2024_predictions/
Dave Täht CSO, LibreQos
parent reply other threads:[~2024-02-25 16:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <65d9fa7c.170a0220.556d0.d465SMTPIN_ADDED_MISSING@mx.google.com>]
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/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6E0n0ZNMj2BnOFWHv1GPAcz6zCC1VR6b6Cj-TTq6+rDg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
/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