StifleR Beacon installation
For more information about what a Beacon Server is and does, see the Beacons Page.
Prerequisites
Operating system
Windows Server 2016 or newer; Windows 10 version 1607 or newer
Runtime
Microsoft .NET 8
Network — inbound TCP 5201
iPerf3 bandwidth measurement port
Network — inbound TCP 5200
FastPing latency check port
Credentials
Local administrator
StifleR Server
Must be running and reachable before the beacon can register
Both ports must be reachable from the subnets whose clients will be measured. If you use Windows Firewall, the installer creates the required rules automatically. For third-party firewalls, open TCP 5200 and TCP 5201 inbound.
iPerf3 is included. The beacon installer ships iPerf3 as part of the installation. You do not need to install iPerf3 separately on the beacon, nor on client machines — the StifleR Client agent ships its own copy.
Installation Steps
Download the beacon installer (
StifleR.Beacon.x64.msi) from 2Pint Software.Run the installer from an elevated command prompt or right-click → Run as administrator.
Accept the license agreement and choose a destination folder (default is
C:\Program Files\2Pint Software\StifleR Beacon).Click Install. The installer registers the beacon as a Windows service and starts it.
After installation completes, open the StifleR Beacon Config Editor from the Start menu or the installation directory.
Set StifleR Server (under Infrastructure) to the URL of your StifleR Server API, for example
https://stifler.contoso.com:9000/.Click Save and restart the beacon service.
Post-Installation: Approving the Beacon
The beacon registers with the StifleR Server automatically on startup. It will not be used for measurements until it has been approved.
Open the StifleR Dashboard.
Navigate to Administration → Infrastructure Services.
Find the newly registered beacon (it will show Pending status).
Click the beacon entry and select Approve.
Once approved, the beacon appears on the Beacons page and is available for assignment to network groups, locations, or areas.
Verifying the Installation
After approval, confirm the beacon is healthy:
The Beacons page shows the beacon with an Online status indicator. A beacon is considered online if it has sent a heartbeat within the last 30 seconds (default threshold; configurable in the server settings).
The Infrastructure Services page shows the beacon version and last heartbeat time.
If the beacon shows as offline immediately after approval, verify that the StifleR Server URL is correctly configured in the Config Editor and that the service has been restarted after the change.
Last updated

