Repository navigation
RelayPony Desktop v2.1.0
Companion release to RelayPony 2.0 for Android. Discovery improvements on both ends, plus Wi-Fi
Direct support on Linux.
Discovery
- Broadcast discovery alongside mDNS, sending from every network interface rather than one
guessed default. This is what makes a phone hotspot work. - Fixed listening port (TCP 45789, UDP 45790 for discovery), overridable with
RELAYPONY_PORT.
Previously the port changed every run, which made firewall rules impossible to write. - mDNS now binds every interface. It used to pick the first private address it found — often the
wrong link on a machine with ethernet,docker0,virbr0or a VPN up — and when it found none it
fell back to a lookup that resolves to127.0.1.1on Arch and Debian, silently confining the
advertisement to loopback. Both failures were invisible; both are gone, and the interfaces actually
in use are now reported. - Peer entries show which mechanism found them and over which interface.
Sending without discovery
relaypony send photo.jpg --to "Kevin's Pixel" --host 192.168.43.1Also available in the app as Send by address. The Receive screen lists the addresses this
machine can be reached at.
Wi-Fi Direct on Linux — experimental
Talk to an Android phone with no network in between — no router, no hotspot, no shared Wi-Fi.
relaypony p2p check # can this machine do it at all?
relaypony p2p find # nearby devices
relaypony p2p send file.jpg --peer <mac>Driven through wpa_supplicant, so it needs a driver advertising P2P-GO and P2P-client and
permission to read wpa_supplicant's control socket — p2p check reports exactly what is missing and
how to fix it. Linux only; macOS has no public API for it and the Windows one isn't reachable from
the JVM.
Ship state, plainly: discovery works, group formation is unproven. On test hardware p2p check
passes and p2p find reliably lists nearby Wi-Fi Direct devices including phones, TVs and printers.
Forming a group has not yet succeeded end to end on any machine — the last attempts stalled inside
Android's P2P framework rather than on the Linux side. Expect it not to work yet, and treat
p2p check as the useful half.
If you try it, the failure output includes an ordered transcript of every wpa_supplicant command and
event, which is exactly what an issue report needs.
Diagnostics
relaypony doctorReports interfaces, what discovery bound to and why anything was skipped, which peers were found and
over which mechanism, whether each is actually reachable, and a scan of the local subnet for anything
discovery missed. Ends with firewall commands for firewalld and ufw when nothing turns up.
Upgrading
Nothing to do — identities, pairings and the transfer format are unchanged. Older builds remain
discoverable over mDNS; the broadcast mechanism needs this version on both ends.