REPRODUCIBILITY: 100%
OS VERSION: 5.2.0.15
HARDWARE: Jolla Phone (jp2601, “Jolla Phone 2026”), SoC MediaTek MT6858, kernel 6.12.38-4k
UI LANGUAGE: English
REGRESSION: No — WireGuard is a 5.0+ feature; this has (as far as I can tell) never worked
DESCRIPTION:
Component: Settings → VPN → WireGuard config import / endpoint parsing.
Steps to reproduce: import a WireGuard .conf whose peer uses an IPv6-literal endpoint in the standard bracket notation:
[Peer]
Endpoint = [2001:db8::1]:51820
Actual result: the stored/displayed endpoint is truncated to [2001 — the parser stops at the first colon inside the brackets, discarding the rest of the address and the port. The tunnel then has no valid endpoint and cannot connect.
Verified: the .conf on disk is intact (cat shows the full [2001:db8::1]:51820) — only Sailfish’s import/parse layer mangles it. [<ipv6>]:<port> is the correct wg-quick / RFC-3986 notation and is accepted verbatim on desktop Linux.
Expected result: endpoint stored/shown as the full [<ipv6>]:<port>.
Workaround: use a hostname endpoint (no brackets, no inner colons) — imports intact. On IPv6-only mobile the hostname must resolve to an AAAA (see the related “uses the unroutable IPv4 endpoint” issue).
Additional information: part of a set of IPv6-only-mobile WireGuard issues found on the Jolla Phone 2026 (SFOS 5.2), filed separately — connmand SIGSEGV on WG connect (thread 30643); mobile data comes up IPv6-only (thread 11917); connman-vpn doesn’t install AllowedIPs routes; and the mobile-data usage counter reads 0 for IPv6-only traffic.