mirror of
https://github.com/wolfSSL/wolfssl.git
synced 2026-10-24 04:09:07 +03:00
532294dcf4
With WOLFSSL_SNIFFER defined, testsuite's simple test and echoserver and the unit test servers in api.c skipped port 0 and listened on the fixed 11111. The exception dates from when the testsuite traffic was sniffed live; the sniffer tests now replay pcap captures and scripts/sniffer-gen.sh drives the example client and server itself, so nothing relies on it. tcp_listen() sets SO_REUSEPORT, so a second process of the same user can listen on 11111 at the same time and the kernel hands it some of our client's connections. testsuite.test never runs under bwrap, and on a shared CI node this shows up as "wolfSSL_connect error -308" right after "listening on port 11111". Reproduced with a decoy SO_REUSEPORT listener on 11111: testsuite fails 5 of 5 runs before and passes 5 of 5 after.