performing-bandwidth-throttling-attack-simulation

Simulates bandwidth throttling and network degradation using tc, netem, and iperf3 for authorized resilience testing.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill performing-bandwidth-throttling-attack-simulation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performing-bandwidth-throttling-attack-simulation
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/network-security/performing-bandwidth-throttling-attack-simulation
Command: npx skills add https://github.com/xalgord/xalgorix --skill performing-bandwidth-throttling-attack-simulation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams need to know how applications, VoIP systems, and monitoring tools behave under degraded network conditions, but guessing is not enough. This Skill provides a structured workflow to simulate bandwidth throttling, latency, jitter, and packet loss in authorized environments so you can measure real impact and validate QoS controls.

Core Features & Use Cases

  • Baseline and Impact Measurement: Uses iperf3 and ping to record bandwidth, latency, jitter, and loss before, during, and after throttling so degradation is provable.
  • Controlled Traffic Shaping: Applies tc, htb, tbf, and netem rules with per-host u32 filters to throttle only target traffic without disrupting management sessions.
  • Progressive Degradation and Slowloris Simulation: Includes a phased throttling script and a Python slow-connection simulator to test connection pool exhaustion and detection thresholds.
  • Use Case: A security team testing a VoIP VLAN progressively adds latency and packet loss, measures MOS at each level, and verifies that QoS prioritizes DSCP EF traffic and that monitoring tools alert on abnormal bandwidth patterns.

Quick Start

Ask the AI to run an authorized bandwidth throttling simulation against a test target, establishing an iperf3 baseline, applying tc netem degradation phases, and producing a degradation impact report.

Frequently Asked Questions about performing-bandwidth-throttling-attack-simulation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I simulate bandwidth throttling on Linux with tc?

Use tc with a token bucket filter, for example 'tc qdisc add dev eth0 root tbf rate 1mbit burst 32kbit latency 50ms', to cap bandwidth on an interface. Combine with netem to add delay, jitter, and packet loss for realistic degradation.

How to test VoIP resilience to network degradation?

Establish an iperf3 UDP baseline for jitter and loss, then progressively add latency and packet loss with netem while measuring call quality (MOS). G.711 needs about 87 Kbps, so throttling below that threshold will break calls.

Why does my tc throttling rule have no effect?

tc shapes egress only on the interface where the qdisc is attached. To throttle traffic toward a victim, apply the rule on the forwarding interface or use an ifb/ingress redirect for inbound traffic.

How do I throttle only one host without affecting my own session?

Use htb classes with a u32 filter matching the destination IP, such as 'tc filter add dev eth0 parent 1: protocol ip u32 match ip dst 10.10.20.10/32 flowid 1:10'. A blanket tbf rule would also throttle your own SSH or management traffic.

When should I not run bandwidth throttling simulations?

Do not run them on production networks without written authorization and a maintenance window, against critical infrastructure without safety controls, or to cause denial of service. Always remove qdisc rules afterward with 'tc qdisc del dev eth0 root'.