Package: wormhole-william Version: 1.0.7-1+b5 Severity: normal X-Debbugs-Cc: [email protected]
Unlikes magic-wormhole or wormhole-rs, there is an issue with wormhole-william, where it fails to establish direct p2p connection between sender and receiver. Receiving side has IPv4 and IPv6 public addresses. Sender is behind IPv4 NAT. magic-wormhole and wormhole-rs work fine, (in any combination of sender and receiver), and easily get 200MB/s due to proximity of client and server (1.16ms rtt), but using wormhole-william, it always goes via a transit server, (aka transit.magic-wormhole.io aka 45.33.13.8), which is somewhere in central US, where in my case both sender and receiver are in central Europe (134ms rtt from either sender or receiver), explaining speed too. -- System Information: Debian Release: 13.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.27-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_SOFTLOCKUP Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages wormhole-william depends on: ii libc6 2.41-8 wormhole-william recommends no packages. wormhole-william suggests no packages. -- no debconf information
