79a3604ac406202c535b0b1d1bb8519bdd8927d3
The scan loop read its port file on stdin. bcmcmd reads stdin too, so the first call swallowed the rest of the file and the loop ended after a single port. Nothing about that looked wrong. The log held one PORT marker and one dsc block, the marker-to-dump comparison passed because both counts shrank together, the exit code was 0, and a 445-port scan just finished in seconds. The loop now reads on fd 3 (done 3< "$PORTFILE") and bcmcmd is given < /dev/null. A second check compares the iteration count against the port list count - the marker/dump comparison cannot see a loop that ends early, so it needed a number that does not shrink with it. The Saved: line reports dumps out of TOTAL rather than out of markers. This is the same bcmcmd trap blanton_traffic_linespeed.sh hit at v0.3.1, where only the first VLAN was configured. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM
Description
Blanton Tera Term TTL reliability test
4.2 MiB