Update the dependency and its transitive modules. Xray moved PacketConnWrapper from transport/internet to common/net, so refresh the references in the TUIC and Juicity outbound comments.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The TUN inbound that replaces the external TinyTun process needs a device
and an IP stack before it can hand anything to the dispatcher. This adds
both behind a stack-independent contract (Handlers: one TCP callback per
accepted connection, one UDP callback per datagram with a reply function
that chooses its own source address) so the stack can be swapped without
touching the forwarding code that follows.
The stack is mipstack in transparent mode: it owns no address, admits every
unicast packet the device delivers and answers from whatever address the
application dialed. The interface address belongs to the operating-system
side of the link and is deliberately not registered with the stack —
mipstack routes packets to its own addresses into an internal loopback, so
replies would never reach the device. The core configures that address on
the interface itself (netlink on Linux, winipcfg on Windows, SIOCAIFADDR on
macOS); other platforms compile but report ErrUnsupportedPlatform.
Tests drive the stack through wireguard's channel device: a SYN gets a
SYN-ACK back and, once the handshake completes, the TCP handler runs with
the right flow; a UDP datagram reaches the handler and a reply from a third
address leaves the device with that address as its source, which is what
full-cone NAT needs later. Both run for IPv4 and IPv6.
The vendored core/xray submodule is dropped. xray-core is now pinned via a
go mod pseudo-version resolving to v26.7.28 (commit 5ca6f4b7); v26 tags are
not directly resolvable because Xray's module path lacks the /v26 suffix, so
the pin must be made by commit hash. CI workflows and the AUR PKGBUILD no
longer need "submodules: recursive" / "git submodule update".
The juicity and tuic outbounds are ported from softwind to
github.com/daeuniverse/outbound (temporarily replaced with an olicesx fork
pending sticky-ip support):
- Dialer calls use DialContext; the network string is decoded with
netproxy.ParseMagicNetwork instead of a "udp" prefix check, since it may
be binary-encoded via netproxy.MagicNetwork.
- A packetConnAdapter wraps xray's UDP dial result: outbound asserts the
underlay conn to netproxy.PacketConn whose ReadFrom/WriteTo signatures
(netip.AddrPort / string) differ from net.PacketConn, while xray returns
*internet.PacketConnWrapper.
- Update core/xray submodule from v1.260327.0 (v26.3.27) to v26.6.1
- Remove deprecated AllowInsecure field from all protocol structs
- Add PinnedPeerCertSha256 and VerifyPeerCertByName fields (service layer)
- Update ngui (Nuxt) frontend with text inputs for new fields
- Update gui (Vue 2) frontend with text inputs for new fields
- Keep existing PinnedSHA256 for juicity (no duplicate)
- Backward compatible: old allowInsecure params silently ignored
- Run go mod tidy to update dependencies
- Xray-core submodule already pointed to v26.3.27 (d2758a02)
- Synchronized go.mod/go.sum dependencies via go mod tidy
- No code changes required: v26.3.23→v26.3.27 has no breaking changes
for Reality protocol
- RealitySettings JSON tags remain fully compatible with Xray-core
v26.3.27 REALITYConfig