Skip to content

Conversation

@ShawnMcKee
Copy link
Contributor

Summary

Fixes two related issues in fasterdata-tuning.sh: (1) --mode audit reported packet pacing as not applied even when an fq/tbf qdisc was present, and (2) running --mode apply --dry-run could appear to change state by performing actions that were not dry-run-safe.

What I changed

  • iface_packet_pacing_audit: inspects the actual qdisc on interfaces and reports pacing applied if fq or tbf is present.
  • iface_apply_packet_pacing: honors --dry-run (logs intended actions and skips applying qdisc or writing services).
  • Bumped script version to v1.3.6 and added a CHANGELOG entry.
  • Added tests/test-fasterdata-dryrun.sh to assert that --mode apply --dry-run does not apply qdisc and that audit output reflects actual qdisc state.

Reproduction

  1. Run: tools/fasterdata-tuning.sh --mode apply --target dtn --apply-packet-pacing --dry-run — should not modify system or qdisc; logs show "Dry-run: would apply packet pacing...".
  2. After a real apply, tools/fasterdata-tuning.sh --mode audit --target dtn should show "Packet pacing: ENABLED (qdisc=fq|tbf)" when a pacing qdisc is present.

Tests

  • tests/test-fasterdata-dryrun.sh (added) verifies dry-run behavior locally.

Please review; I will update or expand tests if you'd like additional coverage.

…tual qdisc (v1.3.6)

- iface_apply_packet_pacing: skip actions when --dry-run is set and log intent
- iface_packet_pacing_audit: always inspect qdisc to detect pacing (ignore flag state)
- bump version to 1.3.6 and add CHANGELOG entry
- add regression test to verify dry-run behavior
@ShawnMcKee ShawnMcKee merged commit 710468f into master Dec 18, 2025
9 checks passed
@ShawnMcKee ShawnMcKee deleted the fix/fasterdata-pacing-dryrun branch December 18, 2025 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants