Damien/arista-evpn-vxlan-clab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

iperf3 traffic generator sends campus->DC, should be DC->campus (server pushes to client) #58

New Issue
Closed
opened 2026-07-20 16:36:23 +00:00 by Damien · 0 comments
Damien commented 2026-07-20 16:36:23 +00:00
Owner
Copy Link

Problem

scripts/generate_traffic.sh runs iperf3 -c "$server_ip" ... from the
campus host with no -R, so per iperf3 defaults the client sends
and the server receives -- traffic flows campus-host -> dc-server.

That's backwards for what these roles represent: dc-serverN is the
DC-hosted service, campus-hostN is the consumer. A real DC-hosted
service delivers data to the consumer (download), it doesn't only
receive uploads from it.

Fix

Add -R (reverse) to the iperf3 -c invocation so the server
(dc-serverN) sends and the client (campus-hostN) receives, and
update the script's direction labels (server -> client instead of
client -> server) to match.

## Problem `scripts/generate_traffic.sh` runs `iperf3 -c "$server_ip" ...` from the campus host with no `-R`, so per iperf3 defaults the **client sends** and the **server receives** -- traffic flows campus-host -> dc-server. That's backwards for what these roles represent: `dc-serverN` is the DC-hosted service, `campus-hostN` is the consumer. A real DC-hosted service delivers data *to* the consumer (download), it doesn't only receive uploads from it. ## Fix Add `-R` (reverse) to the `iperf3 -c` invocation so the server (`dc-serverN`) sends and the client (`campus-hostN`) receives, and update the script's direction labels (`server -> client` instead of `client -> server`) to match.
Damien added reference feat/telemetry 2026-07-20 16:58:55 +00:00
Sign in to join this conversation.
feat/telemetry
Branches Tags
Labels
Clear labels
containerlab
Containerlab topology et configs
 epic
Epic / Phase de projet
 generator
Infrahub Generator Python code
 resource-manager
Resource Manager / IPAM pools
 schema
Modifications de schéma Infrahub
 telemetry
monitoring configuration with prometheus and grafana
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Damien
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Damien/arista-evpn-vxlan-clab#58
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?