diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-04 14:51:08 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-04 14:51:08 +0200 |
| commit | b53298e339b47c6f0b53ab9fd0cfa3fb7741fc28 (patch) | |
| tree | 7b6be18cf5fb557ca407fd7df3a213be4c06c629 /packages/meshbay-node/tests | |
| parent | 08b0f8d7c457e5e58a31bea2b2e43c9f398a6923 (diff) | |
| download | meshbay-b53298e339b47c6f0b53ab9fd0cfa3fb7741fc28.tar.gz | |
feat(node): log the host candidates the WebRTC answer offers
"DataChannel closed" from a peer and a clean node log look identical: the
answer-ready line reported only the srflx count, not the host addresses.
On a NAT'd host or a VM the sole host candidate is an address no other
machine can route to, and that is exactly the case you cannot see. The
line now reads `... host: 192.168.200.173, 1 srflx`, so "did the node
offer anything routable" is answerable from the journal.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'packages/meshbay-node/tests')
0 files changed, 0 insertions, 0 deletions