Beacons
Overview
A StifleR Beacon is a lightweight Windows service that acts as a fixed measurement endpoint on your network. StifleR clients (specifically the elected Red Leader for a subnet) run iPerf3 bandwidth tests against the beacon to determine the maximum available throughput between that subnet and the beacon's location.
Deploy beacons on servers from which clients typically receive bulk content — for example, ConfigMgr distribution points, datacenter file servers, or cloud egress nodes. A beacon placed alongside your content source gives the most representative measurement of what clients actually experience.
Measurement results are stored per network group and feed directly into bandwidth throttling decisions. Instead of a hard-coded cap, StifleR can limit downloads to a configurable percentage of the measured maximum.
How Measurements Work
Scheduled measurements
The StifleR Service runs a continuous measurement loop:
Every 30 minutes, it scans all network groups and queues any that are due for a new measurement.
A network group is queued if all of the following are true: - A beacon is reachable from the group (see Beacon Assignment below) - Beacon measurement is enabled at both the server level and the network group level (see Configuring a Beacon Server) - The group has not been measured within the configured measurement interval (default: 6 days)
The StifleR Service instructs the best-connected client on that network group (preferring 10 Gbps → 1 Gbps → 100 Mbps links) to run a measurement.
The client runs iPerf3 in reverse mode: the beacon sends data, the client measures download throughput.
The result is stored as a maximum bandwidth figure on the network group.
Ad-hoc measurements
Clicking Measure now on a network group in the dashboard triggers an immediate measurement. This bypasses the 30-minute schedule and takes priority over any queued scheduled measurements. The result appears in the Beacons table within a few seconds.
Beacon Assignment
When the StifleR Service looks for a beacon to use for a network group, it resolves the assignment by walking the topology in priority order and returning the first match:
1
Network group
Beacon explicitly assigned to this network group
2
Location
Beacon assigned to the parent location
3
Area
Beacon assigned to the parent area
4
Default
Beacon marked as the global default fallback
A beacon does not need to be marked Default unless it should serve network groups with no explicit assignment at any topology level. Assign beacons as close to the target groups as possible for the most representative measurements.
If no beacon is found via any of these levels, the network group is silently skipped until an assignment is made.
Client-Side Requirement
The StifleR client agent must have the Bandwidth Measurement capability enabled in its feature set to accept and act on measurement requests from the server. This is enabled by default.
What the Beacon Measures and Reports
The beacon itself does not run measurements — it is a passive iPerf3 server. It does, however, count measurements by monitoring its own iPerf3 process and reports the running totals (Measures Started and Measures Completed) to the StifleR Server with each heartbeat. These counters are visible in the dashboard under Administration → Infrastructure Services.
Measurement results are stored on the network group and visible in the Network Groups view, along with the date and time of the last measurement.
Last updated