Changelog
Notable changes to LinkProven — called PingPair before 1.0.0. The format follows Keep a Changelog; releases use Semantic Versioning. The full source-level history lives in CHANGELOG.md.
iPhone app 2026-11-08
LinkProven for iPhone is on the App Store: your synced reports, dashboard and devices, with export and read-only share links.
Privacy policy and terms 2026-11-03
The privacy policy and the terms now cover the iPhone app, including where it keeps your sign-in.
Privacy policy and terms 2026-11-01
The privacy policy and the terms now cover the Android app, and the terms now cover accounts and the portal.
2.5.1 2026-11-21
A Server no longer waits for ever on a Client that connects and then goes quiet, plus two cloud fixes for team workspaces (the full list is in CHANGELOG.md).
Security
- A Server lets a connected Client go after 3 minutes without a step of the sweep, so a device that connects and goes quiet can no longer keep the Server (and, on Windows, its test network adapter) taken. The Linux agent does the same; the agent token with
--allow-fromis what keeps other devices off. - The Server only runs case lengths the Config page allows (1 second to 1 hour).
- Cloud: in a team workspace, one member can no longer hide another member's failed test point, and only the member who uploaded a run (or a workspace owner) can save it again.
Fixed
- A Client the Server lets go mid-sweep is shown on the Server as a sweep cut short, and the Client shows the Server's reason when it receives it.
2.5.0 2026-11-21
Both ends of a Linux agent connection now prove the agent token. Without a token nothing changes (the full list is in CHANGELOG.md).
Security
- The Linux agent proves the token to the laptop before any case runs, so a machine without the token can no longer run a sweep and send back made-up Server results.
- Every control message after the token check is signed: a message changed, replayed or reordered on the way ends the sweep, and both ends say it was tampered with.
- A recorded sign-in to the agent can't be replayed, not even after the agent restarts.
- The web portal enforces a Content-Security-Policy.
Changed
- With a token, the agent and every laptop that uses it must all be on 2.5.0 or later. After updating, run the Linux server set-up again. A laptop with a token saved refuses a Server that can't prove it; clear the token to use a Windows LinkProven Server at the same address.
Fixed
- The Windows Server refuses to listen on every network (
0.0.0.0). - An iperf3 error containing
<no longer stops a Multi-Client PDF from saving. - A malformed number from the Server no longer loses the cases already measured.
2.4.2 2026-11-21
A build-security patch, plus the cloud's half of the session pairing (the full list is in CHANGELOG.md).
Security
- Every package inside the app is pinned by version and SHA-256 when the release is built, from ready-made packages only, so a package changed on the download server cannot reach a release.
Changed
- The portal's dashboard, campaign status and trends count each test point of a session once, paired with that point's own report.
2.4.1 2026-11-21
Each test point in a session counts once, and the Server's serial number is now opt-in (the full list is in CHANGELOG.md).
Security
- A Windows Server sends its serial number to the Client only when Send this laptop's serial number to the Client is ticked (off by default). Make, model, network card and link state still reach every report.
Changed
- A session records each test point's own run id, so the history, campaign status and cable history count each test point once, labelled or not.
- "Save report now" after a session files the last test point under its own label and cable.
Fixed
- A damaged entry in a session report no longer shifts the later test points' results.
2.3.9 2026-11-20
A whole-app security and correctness review, plus a dependency audit (the full list is in CHANGELOG.md).
Security
- The Server window shows a Client's sweep name as plain text, never as formatted text.
- LinkProven's PowerShell calls load only Windows' own modules, and the installed app ignores Qt plugin paths from the environment.
- Updates download inside the install folder, which only administrators can change.
- The team invite email uses an up-to-date mail library, and only workspace owners can delete a campaign or remove a laptop.
- The portal always uses HTTPS, and its share dialog says the shared reports include IP addresses and computer names.
Fixed
- A case is no longer PASS when one of its reference limits could not be checked; jitter and UDP loss limits no longer apply to TCP runs.
- NIC power saving reads correctly on non-English Windows.
- Config files saved with a byte-order mark import, and a non-UTF-8 file shows an import error instead of crashing.
- Excel sheets format numbers the same way, and reports with very long names save.
2.3.8 2026-11-19
A Stop on the Client now reads as a stop on the Server (the full list is in CHANGELOG.md).
Fixed
- Pressing Stop on the Client, or closing it mid-run, no longer looks like a lost connection on the Server: it says "Stopped by the Client", with no orange banner and no sound. A real drop still raises the banner.
- The stop is not lost on a Windows Server: the Client waits for the Server to hang up before it closes.
2.3.7 2026-11-19
The follow-ups to 2.3.6 (the full list is in CHANGELOG.md).
Changed
- Only one thing uses the network adapter at a time: a sweep, a Multi-Client or screening run, a Setup fix, Reset and an update install each take it, and only the one holding it can give it back.
- A busy Server says why it turned a Client away: a Setup fix, an update install or a test of its own.
- An update on the Server laptop installs at once, and a Client that connects while it prepares is told why it has to wait.
- The Server shows "Client connected" only once the Client has passed the handshake.
- Filename patterns: only the six named fields are special, and
{{/}}are a single brace in every pattern.
Fixed
- Fix all keeps the network adapter until its last fix is done, and a Setup fix or Reset waits for the laptop readiness fixes.
- Restarting the Server listener no longer ends the new session's keep-awake hold.
- Cloud uploads always read the current list of waiting reports.
2.3.6 2026-11-19
The follow-ups to 2.3.5 (the full list is in CHANGELOG.md).
Changed
- Campaign files keep the names they always had: "A - B" is saved as
A---B.jsonagain, and a file 2.3.5 saved asA-B.jsonis moved back when LinkProven starts.
Fixed
- Renaming a campaign to a name that only differs in punctuation or case no longer deletes it.
- Updating the Server laptop no longer closes it under a sweep that started while the update was being prepared.
- The Server refuses a sweep while a Setup fix is changing its network adapter, and says it is busy instead of showing a connection error.
- Analysis opens without a pause on a full Reports folder, and the Cables list catches up when you come back to the tab.
- The Cloud panel no longer re-reads every queued upload each time it repaints, and editing a test point's label saves the campaign once.
2.3.5 2026-11-18
Fixes found on a two-laptop bench and in a review of the whole app (the full list is in CHANGELOG.md).
Fixed
- Numbers no longer wrap in report tables: a loss of
0.000no longer prints as "0.00" over "0". - An empty field no longer leaves a double separator in a report name, and a campaign called "A - B" is saved as
A-B.json. - The Plan page no longer overwrites changes made to the campaign file outside LinkProven.
- "Use last run" is greyed out until a sweep finishes and points at Load from report…, and Save Options shows the file name a save will use.
- Loss read from iperf3's text output now comes from the packet counts, and unrecorded NIC counters never read as 0 errors.
- A session's test points no longer count twice in the history.
- The Server laptop stays awake for a whole sweep, and a user Stop no longer reads as a disconnect.
- Setup fixes and Reset run without freezing the window and refuse to run during a test. Firewall rules and the Ping summary work on non-English Windows.
- An update that finishes downloading during a sweep waits for you instead of closing the app.
2.3.4 2026-11-08
Small fixes to how reports are written (the full list is in CHANGELOG.md).
Fixed
- A run's
.jsonrecord and a soak summary are written through the file the app just created, never reopened by name. - A session certificate that can't be written is named without a stray leading space.
- A temporary file that can't be deleted after a failed write, and a failed anonymised copy, are now recorded in the log.
2.3.3 2026-11-02
One report that can't be written no longer stops the rest (the full list is in CHANGELOG.md).
Fixed
- A sweep, session or Multi-Client save keeps going past a document that fails. The other files are still written, what saved still uploads, and the screens say what saved and what didn't.
- A half-written Word or Excel report can no longer be left in the folder or listed as saved.
- With one report per test point on, each test point still saves if another one or the session report fails.
- A hands-free Multi-Client run isn't held by a dialog when part of its report can't be written.
- Runs with photos name the run's folder in messages and Open folder, not its
Photossubfolder.
2.3.2 2026-11-02
Fixes saving reports in the Windows app. Update if you use 1.2.0 or later (the full list is in CHANGELOG.md).
Fixed
- The installed app can save reports again. From 1.2.0 to 2.3.0, saving a sweep or session with the integrity QR on (the default) and Word or PDF ticked ended in "Not saved": only the
.jsonrecord was written and nothing uploaded. Multi-Client reports and Analysis exports were not affected.
Changed
- Every build now has to prove it can save: the packaged app saves made-up reports through the real save code, and a build that fails can't be released.
2.3.0 2026-10-29
History index: the Windows app reads your saved reports once, in the background, and every page agrees on them (the full list is in CHANGELOG.md).
Changed
- The Plan page, Analysis, the Cable ID suggestions, a retest's earlier attempts, the session timeline, "Next" and the handover pack share one index of the Reports folder. It re-reads only reports that changed and does so off the window's thread, so a big folder (or one on a network share) no longer stalls a page.
- A run you just saved counts at once, and the Plan page says "Reading the saved reports…" until the first read after launch lands.
Fixed
- Renaming a campaign no longer loses its status, and re-saving an old run no longer makes it the newest result: runs are ordered by when they started.
- An anonymised copy no longer counts as a test point's result.
- One damaged report can no longer blank the other pages, and a network share that drops for a moment keeps what the app already knew.
- The handover pack says why a record was left out, and leaves out a run folder that links somewhere else.
2.2.0 2026-10-29
Accounts: sign in with an email and a password, or with Google or Apple, in the Windows app and on app.linkproven.com (the full list is in CHANGELOG.md).
Added
- Email and password sign-in in the app (Save Options → Cloud sync) and on the portal, with Create account (name, email, password, then a 6-digit code) and Forgot password?. If you used emailed codes before, set your first password with Forgot password.
- Continue with Google / Continue with Apple, in the app and on the portal.
- Your name on the Account page and in team member lists, and Change password.
Changed
- Every LinkProven email carries a code to type and no link, so company mail scanners cannot use it up first.
- Changing your password signs you out everywhere else, the app included; from a session older than a day it asks for an emailed code first.
- The privacy policy now covers passwords and Google / Apple sign-in.
Fixed
- Continue with Google / Apple in the Windows app now opens your browser (Windows dropped the sign-in address before).
- A cancelled Google or Apple sign-in can no longer sign you in later, and offline errors read plainly on the portal.
2.1.0 2026-10-28
Portal hardening: your account and your team, on app.linkproven.com. The Windows app is unchanged apart from the version (the full list is in CHANGELOG.md).
Added
- Delete your account yourself (Account → Delete account). It closes at once; your personal workspace and any team where you are the only member are erased 30 days later. Runs you uploaded to a team stay with it, and while you are a team's only owner, you hand it over first.
- Team invites are emailed from invites@linkproven.com, with Email again to resend.
- Every share link in one place: a workspace's owners see all live links and can revoke any of them.
Changed
- A team always keeps an owner, and the server's file checks no longer stall on a file it cannot read.
- The privacy policy now covers deleting your account and invite emails.
Security
- Invite emails are fixed text with limits on how many go out, so they cannot be used for spam or phishing; a closing account cannot create anything that would outlive it.
2.0.0 2026-10-28
Portal: everything the web portal needs, in the app and on the server. It runs on the hosted LinkProven service (Frankfurt, EU), and nothing leaves a laptop until you sign in and turn uploads on (the full list is in CHANGELOG.md).
Added
- The LinkProven portal at app.linkproven.com: sign in with an emailed code and see every synced run. Dashboard, reports, campaigns and laptops; compare runs side by side; trends per test point; a ZIP export whose manifest checks every file; share links that expire; and team workspaces you join only by accepting an invite.
- Every stored report is checked by the server, which re-hashes the file and shows verified or, in red, does not match.
- Upload existing reports and Upload to (Save Options → Cloud sync): send the runs you saved before syncing, after you have seen how many, and pick the team workspace they go to.
Changed
- A re-saved run no longer re-sends files the account already has, which saves the field link.
- The privacy policy now says what cloud sync and the portal store, where (the EU, Frankfurt) and for how long.
Security
- Uploads are limited per user and per workspace; share links are stored only as hashes and never show the laptops or their addresses; nobody joins a team without accepting.
1.7.0 2026-10-27
Reach: a command palette and a touch mode for rugged tablets (the full list is in CHANGELOG.md).
Added
- Command palette (Ctrl+K): one search box over every page, the run actions, your saved profiles, recent reports, the appearance and role settings and every Help section. Each command does exactly what its button does, and one that can't run right now says why.
- Touch mode (Setup → Appearance → Touch): 44-pixel targets, bigger check boxes, flick scrolling, swiping between tabs and press-and-hold for any tooltip. Auto turns it on when a tablet or 2-in-1 is held as a tablet; a touch-screen laptop that doesn't fold stays as it is.
Security
- Folders and files LinkProven opens for you (reports, logs, licences) now open as you, never with the administrator rights LinkProven runs with.
1.6.0 2026-10-27
Test types: honest TCP results, verified DSCP marking and replaying a saved run (the full list is in CHANGELOG.md).
Added
- TCP retransmits, round trip and congestion window for every case and every second, read from Windows itself while the case runs. Reports show Retransmits and TCP RTT where a UDP run shows jitter and loss; a case that could not be read says not recorded, never zero.
- DSCP marking (EF, AF41, CS6, CS0 or any value 0–63) through a temporary Windows QoS policy, removed when the sweep ends. The report says whether the marking was verified leaving the laptop, not marked or not checked.
- Replay a run from Analysis: every setting that changes is listed first, this laptop's network settings stay, and Undo replay puts yours back.
Changed
- A TCP run's jitter and loss read — (not measured) everywhere, including runs saved before 1.6.0; they used to read 0.000, like a perfect UDP run.
- The Validation grid and verdict line judge with the same code and inputs as the sweep itself, and Analysis no longer compares a UDP run with a TCP run case by case.
1.5.0 2026-10-26
Hardening: one judgement per case, a locked-down Linux server agent and soaks that survive a power cut (the full list is in CHANGELOG.md).
Added
- Linux agent token (on by default): the agent refuses any Client that cannot prove this laptop's token. The token itself never crosses the network. Copy and Paste move it to a second Client laptop.
- With a Client address set, the Linux agent serves that address only and refuses every other one, even with the server's firewall off.
- A screening run or a soak round says so on the Server page and in its witness view.
Changed
- The Linux agent's Python packages are installed at pinned versions and file hashes, from a list inside the checksum-verified agent.
- One judgement per case: the Validation grid, the timeline, the verdict line and the Server mirror all show the judgement made as each case finishes, against the baseline active when the run started (the one the saved report uses).
- The soak summary is written after every round, so a power cut overnight still leaves the rounds so far.
Fixed
- A refused agent token no longer reads as a connection error; re-running the Linux set-up restarts the agent; a failed package install no longer leaves an agent restarting in a loop.
- A soak whose summary could not be written for a round no longer starts a second folder.
1.4.0 2026-10-26
Operations: the run seen from both ends, quick triage, overnight soaks and Linux servers (the full list is in CHANGELOG.md).
Added
- Live mirror on the Server laptop: the Client's case matrix, timeline and running verdict, with no extra traffic on the link under test. An older Client still gets the cases coloured from the Server's own counts.
- Witness view (F11): the run full window in large type, for someone standing a few metres away.
- 2-minute screening: four short cases to triage a cable. It never gives PASS or FAIL, only Looks clean or Worth a full sweep, and its reports say SCREENING.
- Soak runs: repeat the sweep every N minutes for H hours, or from a set time. Each round saves its own report, plus a soak summary with the worst case and when it happened. The laptop stays awake while any test runs.
- Linux servers: one setup script installs iperf3 as a reboot-proof service, and the optional LinkProven server agent lets a Linux machine answer Single-Client sweeps with Server-side evidence. The script checks the agent's SHA-256 before installing it.
- Getting started checklist on Setup, status chips that act, and empty pages that offer the next step (including demo data in Analysis).
- Low light theme, Compact density, a pinnable rail, and remembered splitters, tabs and Analysis ticks.
Changed
- One poller per network card now serves the link watch, the disconnect monitor and the per-second counters, and the Validation grid, the timeline and the Server mirror judge cases with the same code.
- The
.jsonrecord is schema 12;run_kindmarks screening runs and soak summaries, which never count as acceptance.
Fixed
- The end-of-run summary could crash when cable validation was off and no reference was armed.
- A long server-command block on Multi-Client was squeezed behind a scrollbar.
Security
- The Linux agent refuses to listen on every interface; text from the peer is cleaned before it reaches the agent's log; a checksum mismatch in the hand-pasted commands removes any older agent copy.
1.3.0 2026-10-25
Insight visuals: see where packets were lost, when, and on which cable (the full list is in CHANGELOG.md).
Added
- Insight charts on Single-Client → Results, filled case by case: where the packets went (each loss placed on the cable or inside the receiving laptop, by the same rule as the verdict), delivered vs offered, seconds by datagrams lost (a laptop burst or a cable dropping a few every second), jitter by payload, ping round trip per second, and both laptops' card counters per second.
- A session chart in continuous mode: each test point and its retries to scale, the points still to run, and the time to the end of the plan.
- A train map on the Plan page: type the cars and every test point is drawn where it runs, coloured by its latest verdict.
- Loss fingerprints: a tiny payload × bandwidth grid beside each run in Analysis and each attempt in a cable's history, and a live link pulse on the Validation tab while a case runs.
- Insight charts in Word/PDF (Save Options, off by default). With the option off, every document is exactly as 1.2.0 wrote it.
Changed
- The
.jsonrecord is schema 11; the new per-second keys appear only when a run recorded them, so older readers see the cases they already knew.
Fixed
- The live link pulse starts neutral (grey) until a case's loss has been counted, instead of reading as "nothing lost".
Security
- Per-second data read from saved records, campaign files or the Server is size-capped, so a malformed or oversized file can't freeze the app.
1.2.0 2026-10-25
Evidence & history: proof a report wasn't changed, and every run of a cable in one place (the full list is in CHANGELOG.md).
Added
- Integrity on the cover: every Word and PDF report carries the SHA-256 of its
.jsonrecord and a QR code. A phone camera opens the run's summary on linkproven.com/r; the summary lives in the link, so nothing is uploaded. - Verify report (Analysis): re-hashes a run's record and photos and checks the reports beside it were made from it.
- Photos of the cable with captions, shrunk and stripped of camera data, shown in the Word and PDF reports and hashed into the record.
- Per-cable history (Analysis → Cables) and a retest chain: a retest's report lists the earlier attempts and their verdicts, so a FAIL never disappears behind a later PASS.
- A bench-baseline library: several named baselines, one per laptop pair, chosen per campaign.
- Diff, reworked: any two runs as A and B, a payload × bandwidth matrix, and a one-line tally that treats small wobbles as the same.
- A one-page cable certificate, customer report templates (logo, sign-off parties, sections, filename pattern), an anonymised copy to share with a vendor, and a handover pack: one zip per campaign with a
SHA256SUMSfile.
Changed
- The
.jsonrecord is written first, with LF line ends, so its hash is the same on every machine and a report that fails to render can't lose the run's data. - A certificate or anonymised copy made later keeps the verdict the run was saved with, and the customer logo travels with the run folder.
Fixed
- A
/in a cable ID no longer cuts the report folder name short, and the Record details notes box keeps its three-line height.
1.1.7 2026-10-22
Changed
- The version sits under "LinkProven" at the top of the side menu, as the same labelled tag the launch splash and this site show.
- The window's title, and so its taskbar button, is just "LinkProven"; the version is on the tag and in About.
1.1.6 2026-10-22
Changed
- The version is a labelled tag on the launch splash: a pill under the wordmark with a tinted brand fill and outline, instead of faint grey text. This site shows the same tag under the wordmark in its header.
1.1.5 2026-10-22
The first update since 1.0.0: it carries 1.1.0 to 1.1.5 (the full list is in CHANGELOG.md).
Added
- Sounds you choose per event (Tick, Sonar or Retro, or Windows system sounds): run start, each case, retries, the verdict, a saved report, a lost connection. Quiet during a sweep and Do not disturb are respected, and anything that needs you also flashes the taskbar button.
- Notices instead of pop-ups for information, and keyboard shortcuts: Ctrl+1–0 for pages, F5 to run, Esc to stop, Ctrl+S to save, F1 for Help, Ctrl+/ for the list.
- A finished case flashes in the table, and the taskbar button shows the run's progress.
Changed
- A new app icon: the pulse mark on a navy tile (a white tile on light pages), in the app and on this site.
- A report keeps what its run started with: the config, the test point, the cable ID and the rest of the record are taken when the run starts, so editing them before "Save report now" can't relabel the data.
- Closing LinkProven only undoes an IP address LinkProven set; a static address you typed yourself stays.
- Loss reads the same in every format (Excel shows "<0.001" like Word and PDF), and a multi-test-point session is judged on every test point.
- The Config tab keeps changes you haven't applied, and a profile's fping options are limited to ones that can't break the results.
- In-app updates stage inside LinkProven's own folder and check the download's SHA-256 again before installing.
Fixed
- Sounds no longer cut each other off, and an aborted run sounds once.
- Pressing Stop on the Client no longer sounds the disconnect alarm on the Server.
- A failed iperf3 start ends the case at once instead of pinging out its full 30 s.
- Help and About links open your browser as you, not as administrator.
- Many smaller fixes from a full code review, listed in CHANGELOG.md.
1.0.0 2026-10-21
PingPair is now LinkProven. This is the first LinkProven release and a fresh start: it carries everything from 0.8.0 to 0.9.0, and it does not take over a PingPair install's settings.
Changed
- A new name everywhere. The window, side menu, splash, Help, welcome tour and every report format say LinkProven, beside the same pulse mark. Reports link to www.linkproven.com.
- Settings live under
LinkProven, data under%APPDATA%\LinkProven, firewall rules are namedLinkProven … (in)and reports are saved asLinkProven_<time>. - Updates come from github.com/mhmd2520/Linkproven. A PingPair install keeps checking the PingPair repository; install LinkProven alongside it.
- An installer joins the portable .zip, and both are published with a SHA-256 checksum.
0.9.0 2026-10-18
The Campaign release: the app keeps track of a whole train's test points, not one sweep at a time.
Added
- A Plan page for the test campaign — train set, location, contract, procedure, who tests and who witnesses, and the test points. Each test point's status is read from the saved reports, and the page names the next one to run.
- A richer cable record on Single-Client: a test-point picker filled from the plan, cable IDs suggested from the plan and earlier reports (a barcode scanner works), lengths in metres or feet checked against the design length, and conditions, ends and a witness tick under Record details….
- Required fields a campaign can insist on before a validated run.
- A summary sheet replaces the finished popup: the verdict, its four numbers, the files written, what to do on FAIL or REPEAT, and Next / Retest.
- Test kit on the record: each laptop's model, serial, network card and driver, and whether the card is a USB adapter.
- Link drops and speed changes are evidence, watched for the whole sweep; any one fails criterion 1.
- A battery guard asks before a run the battery may not last through.
Changed
- Reports with a campaign carry its record: rows on the cover, a pre-filled sign-off, the train in the running header and extra CSV columns.
- A new logo: two dots and a thin pulse with a soft glow, on a transparent background. The launch splash draws it in 2.2 s — the same intro this website plays.
0.8.2 2026-10-17
Fixed
- The selected page in the side menu is readable again on the dark theme (dark on cyan, 10.4:1, instead of white on cyan, 1.8:1).
- The menu icons take the theme's colours as soon as the window opens.
0.8.1 2026-10-15
Fixed
- The live throughput chart draws while each case runs. iperf3 had been buffering its per-second rows until the case ended, so the chart only ever showed a finished case for a moment.
- The sweep timeline’s “now” line follows the running block, which now fills from its own start; “100%” appears only when the sweep is done.
- No console window flashes during start-up.
Changed
- The splash shows the LinkProven mark in 3D, with the name below it.
- A tidier Single-Client page: level columns and a note asking for the Test point and Cable ID before a validated run. Field hints are written directly.
- Reports mark over-capacity cases with ▲ in the case matrix and explain the high ping times in cases that fill the link.
0.8.0 2026-10-14
Changed
- The window fits a laptop. A left navigation rail replaces the top tab bar (icons only on a narrow window, a dot where a warning is). Every page scrolls and none scrolls sideways; the window now fits down to 860×500, so a 1366×768 laptop at 125 % or 150 % scaling shows every field.
- The run dock: Run / Stop, the status line and progress stay pinned under the Single-Client and Multi-Client pages. Role, link and target sit as chips at the top; a warning collapses to a chip.
- Reports open on their verdict. A PASS / FAIL / REPEAT / INCOMPLETE tile, four key numbers and the Table-2 row on the cover; page numbers, a running header and a sign-off block (Tested by / Witnessed by); one palette and font across all five formats; Excel opens on a Summary sheet.
Added
- Run visuals: a case matrix (verdict, loss, % offered or latency; click to pick cases), throughput as % of offered, latency range, wire load per case, reference bands, the link diagram with the 100 m channel limit, “Did the cable deliver?”, and a sweep timeline in place of the bare progress bar. Analysis gains a Matrix and a “vs Baseline” view, Setup a readiness ring, Multi-Client a bar per simulated client.
- An installer (
LinkProven-0.8.0-setup.exe): Program Files, Start-menu and desktop icons, reports inDocuments\LinkProven. The portable folder still works, and now shows onlyLinkProven.exeandReports. - CSV gains
test_point,cable_id,case_resultandcable_deliveredfor a validated run.
Fixed
- A multi-segment report judged every test point’s reference on the first segment’s cases; each test point is now judged on its own.
0.7.5 2026-10-14
Fixed
- A verdict rests only on evidence the run actually has. Pressing Stop no longer shows FAIL on screen while the saved report says INCOMPLETE; a missing network-card count reads “not recorded”, never 0; laptops that did not settle no longer excuse a short card count; and the link capacity is the slower laptop’s, so a 1000 / 100 Mb/s pair is no longer failed on throughput.
- Both laptops count card traffic over the same span, so a few control frames counted on one side only can no longer hide frames the cable dropped.
- The live grid colours each case from the same judgement as the verdict — loss limit, bench baseline and earlier attempts included. A cell with no datagram count reads “n/a”, not a green 0.
- “Validation off” means the old reports again: no laptop snapshots, NIC counters, warm-up or retries are recorded. Reports also record the Server address the cases really ran against.
- A bench baseline can no longer come from a single-PC session, a run with validation off, or a report older than 0.7.
- A warm-up that measures nothing stops at once and shows the real error; a link that drops during the warm-up stops with the “cable unplugged” message; a stopped or failed retry no longer replaces the measured attempt; Stop, close and role switches no longer wait out a slow PowerShell probe.
- The “External IP change detected” dialog no longer opens over the launch splash.
0.7.4 2026-10-14
Changed
- Cable validation is on by default. Every two-laptop Single-Client sweep gets the warm-up, retries and the Table-2 verdict without a trip to Config. A Loopback (single-PC) run is never judged — there is no cable.
- UDP buffer default 2 MB (
-w 2048K): about 0.2 s of cushion at the heaviest case, covering a pause seen on the bench. With fping’s 1 s timeout the larger send queue costs only ping latency, not lost pings. - iperf3 and fping run at Windows high priority (Config → Test plan, on by default), so Defender, Windows Update and indexing pause them less often.
- A lossy case is retried up to twice (was once), stopping at the first clean attempt; every attempt stays in the report.
- Each test point carries its own Cable ID, asked for between segments and used in that test point’s Table-2 row and report.
Fixed
- A clean retry no longer washes out a cable fault: a case whose card counts came up short is not retried, and an earlier attempt the cable did not deliver fails the case.
- A run stopped part-way reads INCOMPLETE, never PASS on the cases it managed; a case with no throughput reading or nothing received is “not recorded”; a loss below 0.001 % prints “<0.001”, never “0.000” beside a FAIL; TCP and Loopback runs are never judged.
- The Client’s “Server host” now reaches iperf3 and fping, not only the control channel; a docked laptop’s office adapter is no longer taken for the test adapter; “Apply all fixes” is refused during a sweep; the Ping tab counts only real replies.
- Multi-Client binds to the client IP only when this PC holds it, and its report times are the run’s own.
Security
- Text from the other laptop or the user can no longer inject markup into the PDF or a live formula into Excel; protocol errors no longer echo the peer’s value; a profile can no longer pass fping
-f,-gor a network path.
0.7.3 2026-10-13
Fixed
- fping now waits 1 s for each reply (
-t 1000, Config → Test plan → fping Timeout). In count mode fping waits only the-pperiod — 10 ms — so every reply slower than that had been reported as a lost ping, in every version. At 90 Mb/s a full link queue made most replies slower than that, though the Client’s card received them all. Expect ping loss near 0 and higher, true, maximum ping times in the 70–90 Mb/s cases. The bench lesson →
0.7.2 2026-10-13
Changed
- UDP buffer default 1 MB.
-wsizes both directions, so 0.7.1’s 4 MB was also the Client’s send queue: in cases that filled the link each ping waited ~0.4 s behind it, past fping’s timeout. (Raised to 2 MB in 0.7.4, once fping waited longer.)
Added
- UDP socket buffer table in the report’s evidence: the size each case asked for and the receive buffer the Server’s iperf3 actually got.
0.7.1 2026-10-13
Changed
- The sweep asks iperf3 for a bigger UDP buffer (
-w; Config → Test plan → UDP buffer). In every lossy bench case the Server’s network card had received every packet the Client’s card sent: Windows’ default 64 KB buffer — about 10 ms of 200 B traffic — was dropping them inside the laptop. The bench lesson → - REPEAT when the cable is proven to have delivered every packet. Each case compares the two cards’ counters; when every failing case balances and no card counted a damaged frame, the verdict is REPEAT, not FAIL. A short count or any NIC error stays a FAIL.
- The warm-up is judged on loss and NIC errors. The average-ping limit is optional and off by default — settled laptops on good cables averaged 1.5–2.5 ms.
Added
- A Cable delivered column in the case-by-case table, Server card received in the evidence section, and amber “lost inside a laptop” cells on the Validation sub-tab.
Fixed
- The evidence section no longer says a loss spread across a case points at the cable — the bench lost datagrams spread over 26 of 31 s that the Server’s card had received. The column is now When, and the card counts decide.
0.7.0 2026-10-12
Added
- Cable validation (Config → Cable validation). Every Single-Client report can lead with a verdict for the cable — PASS, FAIL, INCOMPLETE or REPEAT — judged on four criteria: both adapters at the expected speed in full duplex, no lost pings, every case at 99 % of the throughput it can deliver with no UDP loss, and no NIC errors. A case that asks for more than the link can carry is judged on loss only. (Off by default in this release; on since 0.7.4.)
- The Table-2 row, ready to copy — Test point, Cable, Loss %, Pass / Fail and a one-line Comment — in Word, PDF, text and Excel.
- Laptop readiness on the Setup tab: mains power, Windows power mode, Receive Buffers, energy-saving adapter features, Speed & Duplex and the link, with “Apply all fixes…” after you confirm the exact list.
- Link and laptop evidence in every report, a warm-up before the sweep, a retry for a lossy case, a bench baseline, a live Validation sub-tab, and test-point sessions with a
{tp}filename token.
Changed
- The sweep sidecar is schema 7 — all additions, so older readers ignore them. A 0.7 laptop still works with an older one; the missing evidence reads “not recorded”.
Fixed
- Stopping a continuous run no longer strands its finished segments — you are offered to save them as the session report.
- The save dialog said
{time}gives HHMMSS; it gives HHMM.
0.6.3 2026-08-25
Changed
- The product description now matches what the app does. It still promised a fixed 20-case test between two laptops, which stopped being the whole story once the grid became editable, the Multi-Client tab arrived, and Loopback made a second machine optional. LinkProven now “automates latency and throughput testing on your network — configurable sweeps, multi-client load tests, or a single-PC run — and turns every test into a ready-to-file Word, PDF or Excel report.”
- The Quick Start tour and the capability cards follow suit. The tour opens on a configurable grid of test cases — 20 by default — rather than a fixed 20-case test, and says “machine” where it used to say “laptop”; the two ends have been able to be VMs or embedded computers for a long time.
- The user guide frames the 4 × 5 grid as the default it is, not the only grid, and points at the Config tab for changing it.
Fixed
- Two timing figures left over from 0.6.0. That release cut a full sweep from ~16 minutes to ~11, but the documentation still quoted the old numbers — “16 minutes for the full 20 cases” online, and “~50 s” per case in the user guide. Both now read the real ones (~11 minutes, ~31 s per case).
0.6.2 2026-08-19
Fixed
- A Multi-Client run is no longer reported as a corrupt file. These runs are deliberately kept out of the Analysis tab, which compares 20-case sweeps — but that exclusion was signalled with the same error as an unreadable file, so a perfectly good report was counted as a parse failure. “Not a sweep” is now its own signal; a sidecar that really is unreadable still warns.
Added
- Saving a report set is recorded in the log — one line naming the folder and the formats written, so a run’s output leaves a trace. That matters most for an automatic save nobody pressed a button for.
0.6.1 2026-08-19
Fixed
- A clean run no longer closes its live log claiming a lost ping. The Multi-Client log counted any line containing “unreachable” as a lost probe — including fping’s own
0 unreachablesummary row — so every run invented one loss, and a 1,886 / 1,886 run ended its log with(1 lost)beside a report reading 0.00 % loss. Only real probe lines are counted now. Every saved number was always correct. - The same section is named the same way in every Multi-Client report format. One run’s Word document headed a table “Per Simulated Client” while its text report headed the same table “Per simulated client”.
0.6.0 2026-08-19
Fixed
- Each case’s latency and loss are measured over the same window as its throughput. fping was asked for more probes than it could send in the time available, so it outlived every case by about 17 seconds — roughly 37 % of each case’s latency and loss sample was taken on an idle link, after the traffic had stopped. Ping figures now describe the loaded link they were meant to describe.
- Watching a sweep no longer competes with measuring it. The live view could take time away from the run it was displaying.
- A control-channel read timeout now bounds the whole call, chart images that fail to write say so instead of failing silently, a truncated capture is flagged rather than returned as complete, and
nan/infcan no longer reach a numeric workbook cell. - The Analysis tab stopped re-walking the reports folder every few seconds, and Fix-all can be interrupted by closing the window instead of driving on against a closing view.
Changed
- A 20-case sweep now takes about 11 minutes instead of about 16 — same measurements, same duration per case, without the dead time.
fping.interval_msvalues below about 16 all produce the same rate on the wire. The setting is unchanged and still honoured exactly from 16 ms upward; it simply buys no extra resolution below that, and the Help tab now says so.
Security
- The updater’s two metadata reads (the release listing and the
.sha256sidecar) are bounded at 4 MiB rather than reading whatever arrives — a guard against a captive portal or a misconfigured mirror, not against a compromised GitHub, which the SHA-256 gate covers.
0.5.1 2026-08-18
Fixed
- The Multi-Client live log no longer stutters. Lines arrived in bursts rather than as they were produced.
- The “Generated by LinkProven” line now closes the report instead of landing mid-document, Word documents are A4 like the PDFs of the same run already were, the workbook’s Packet Loss column stays numeric, and a multi-client sidecar now describes the run it is saved beside.
0.5.0 2026-08-18
Added
- The Multi-Client tab has a live log. The tab used to go silent for the length of a run; it now shows iperf3’s per-second row for every simulated client and a
[SUM]line for the whole load, with one[fping]line per second beside them so a latency spike can be read against the throughput of the same second. - Saving a multi-client report shows a busy indicator while the five formats are written.
Fixed
- Multi-Client PDFs stopped breaking their own tables — they are portrait, centred, and fill the page. Workbook headers keep their units and freeze their header rows, the text report’s numeric columns line up, every document names the build that wrote it, and the five formats now agree on their presentation as well as their numbers.
- A failed run no longer signs off by saying it finished, and an aborted run keeps iperf3’s own words instead of a reassembled approximation.
0.4.5 2026-08-18
Fixed
- A dead server is reported once, not twice, and the connectivity check no longer provokes the very error it was meant to remove.
- “Last sweep” can no longer name the oldest run on disk. Saved sweeps were ordered by file timestamp alone.
Changed
- The shipped screenshots are current and reproducible — rendered from the live app rather than captured by hand, so a UI change can be re-shot in one command.
0.4.4 2026-08-18
Fixed
- A Multi-Client run now ends the moment the far end does, and a physical disconnect is detected in about a second rather than at the end of the case.
0.4.3 2026-08-18
Changed
- A successful connectivity check no longer leaves an error line in the server’s own console.
0.4.2 2026-08-18
Fixed
- The Multi-Client page no longer jumps when you click Run or Save, and saving from the post-run dialog no longer raises a second dialog on top of it.
0.4.1 2026-08-18
Fixed
- A finished Multi-Client run now asks where to save it when auto-save is off — the setting is app-wide, and this tab was ignoring it.
- The per-client results table no longer clips its rows, and the server-command blocks are readable and unambiguous about what each Copy button copies.
0.4.0 2026-08-18
Changed
- Reports open with a cover page, and the LinkProven version is named under the wordmark in every report format.
- Threshold fields on the Config tab hint instead of pre-filling, so an untouched field arms nothing.
- The Server no longer reports a finished sweep as a disconnect.
Fixed
- Sub-1 % ping loss no longer reports as zero. fping rounds its own loss percentage to a whole number, so 7 lost probes of 3,000 arrived as
0 %; the figure is now derived from the counts. - Saved test-plan profiles survive an update. They were being written inside the application folder, which an update replaces.
0.3.0 2026-08-08
Added
- Multi-Client tab — drive many simulated clients at once from this laptop against a single server, to see how its LAN side behaves under realistic multi-workstation load. One parameterised case, a per-client results table, and a live capacity budget that tells you whether this machine can actually generate the load you asked for. The server needs no LinkProven: pick your Linux distribution and copy the generated commands.
- Reference values — set thresholds for throughput, jitter, packet loss and latency, and every result row is judged PASS / MARGINAL / FAIL / NOT EVALUATED. Reports gain a verdict banner, reference columns beside the results, the reference table itself, and an exceptions table listing only the rows that breached. Throughput limits can be a percentage of each case’s offered bandwidth — the only thing that means anything across a 10 → 90 Mbps sweep. Ships with a standards-backed default profile (ITU-T G.114 / Y.1541).
- Threshold lines on the Analysis charts when every selected run was judged against the same reference.
- CSV export of results, for spreadsheets and scripts.
- Saved profiles now carry the network settings, both run modes and the thresholds — a site’s whole test setup in one file, with a one-click picker on the Config tab.
- Help gained Multi-Client and Reference values sections, plus refreshed screenshots throughout.
Changed
- The Run tab is now Single-Client, beside the new Multi-Client tab.
- The Config tab serves both run modes through a selector that follows the active run tab, in a single scrolling column.
Fixed
- Config tab: overlapping toolbar controls, a clipped caption, and a group title colliding with the panel below it at smaller window sizes.
0.2.4 2026-06-26
Changed
- Maintenance release — no functional changes from 0.2.3. Marks the updater fixes (0.2.2 certificate trust, 0.2.3 install/swap) as verified stable on a clean install, and validates the in-app update path 0.2.3 → 0.2.4.
0.2.3 2026-06-25
Fixed
- In-app updates now install correctly. After downloading an update and confirming the restart, the app could close and reopen on the same version — the update silently didn't apply. The background updater no longer locks itself out of its own install step, so the new version is installed and launched as expected.
0.2.2 2026-06-25
Fixed
- Update check now works on fresh Windows machines. "Check for updates" could
fail with "Couldn't reach GitHub" / a TLS certificate error (
CERTIFICATE_VERIFY_FAILED) on a newly set-up Windows PC or VM whose certificate store hadn't yet downloaded GitHub's root CA. LinkProven now ships its own trusted CA bundle, so the update check verifies correctly regardless of the machine's certificate-store state — no more one-time browser/curlworkaround.
0.2.1 2026-06-25
Fixed
- Removed an erroneous "you are running the self-updated build — the updater worked!" banner that appeared on the About tab.
- The Excel comparison export now leaves a 100%-loss case's latency cells blank
— consistent with the Word/PDF/TXT reports — instead of writing a
nanvalue that some Excel versions flagged as a corrupt workbook. - Hardened report generation against rare failures: a branded-header glitch can no longer abort a whole report, and a 100%-loss case no longer skews the per-case analysis charts.
0.2.0 2026-06-25
Changed
- Report headers are now fully branded across every format. Each Word, PDF, TXT, and Excel report — single-sweep and Analysis comparison alike — now leads with the LinkProven logo, a two-tone "LinkProven" wordmark, and a clickable www.linkproven.com link above the title, with a matching site link in the footer.
Fixed
- The Analysis tab's "Loaded runs" list no longer clips or overlaps the run entries on higher-DPI displays. The list now fills its panel, and transient load/parse messages appear in the main-window status bar instead of a cramped in-pane label.
0.1.0 2026-06-09
First public release.
Added
- Automated 20-case Server/Client LAN sweep (fping + iperf3) with Word / Excel / PDF / TXT reports and a JSON sidecar per run.
- Setup prerequisite checker with one-click fixes, role auto-detect, Config test-plan editor, Analysis comparison/diff tab, Help guide, and theming.
- In-app updater: "Check for updates", an every-launch reminder with an opt-out, and "Download & install" that fetches the new build from the GitHub release, verifies its SHA-256, swaps the install, and relaunches — with a live speed/ETA readout and a cancel button.
- About tab reorganized into four cards (About / Updates / Credits & License / Diagnostics).
- The LinkProven logo now appears in the header of every Word and PDF report.
- Packaging: top-level
LICENSE, expanded third-party license notices, and this changelog.
Changed
- Download streamed in 1 MiB chunks (was 256 KiB) for faster transfer.
- The Analysis tab's Export comparison report now writes a single self-contained folder with consistently sized wide charts.
- A sweep is now blocked while Wi-Fi is connected to the test subnet, and the Ethernet adapter is reverted to DHCP when the app closes.
Security
- Update download refuses an
https→httpdowngrade, on top of the mandatory SHA-256 check. The bundle is unsigned for v1 — HTTPS + SHA-256 is the integrity story. - All elevated system-tool calls (
netsh/ping/icacls) are invoked by absolute System32 path, removing a binary-planting privilege-escalation surface. - The NIC override is validated as an IPv4 literal before it reaches
netsh; the report filename pattern is sanitized so it can't write outside the Reports folder.
Fixed
- Self-update now reliably applies and relaunches.
- Closing the window mid-download no longer freezes the app.
- A 100%-loss case no longer renders
nanin latency columns or skews the summary — those latencies now show as "—". - The Analysis tab's Export comparison report now works in every format.
- iperf3 connection errors are recorded as a failed case instead of a misleading 0 Mbps result.
- The server no longer stalls ~10 seconds when a client disconnects mid-case.
- "Reset to defaults" on Save Options restores Word + Excel only (the documented default).
- The Analysis Diff tab's hint banner is now readable on the Light theme.
See every release on the GitHub Releases page.