Releases
v1.1.0
v1.1.0 - WireGuard Egress Backend
Compare
Sorry, something went wrong.
No results found
Added
Added WireGuard as a new egress backend alongside v2rayA system-tun.
Added numeric wizard selections for egress backend and edge mode.
Added WireGuard config import/paste flow in the wizard.
WireGuard configs are normalized for gateway use:
enforces Table = off
keeps IPv4 Address
removes DNS lines to avoid changing host DNS behavior
Added WireGuard activation support via wg-quick@<interface>.
Added WireGuard health checks:
service active
interface exists
recent handshake
Added WireGuard diagnostics to tge-logs.
Changed
tge-ctl --activate no longer starts v2rayA when WireGuard mode is selected.
tge-apply.path is only enabled for v2rayA system-tun mode.
tge-apply now supports wg0 or another configured egress interface as TUN_IF.
GRE health validation now checks local/remote tunnel parameters, tunnel IP, and MTU.
GRE ensure now recreates a TGE-owned GRE tunnel when it does not match the saved config.
Fixed
Fixed GRE mode cases where an old gre-egress interface existed but pointed to stale local/remote endpoints.
Fixed stale tun0 rules when switching from v2rayA system-tun to WireGuard.
Improved WireGuard paste flow in the wizard by requiring explicit END termination.
Notes
WireGuard mode is recommended for higher-throughput gateway deployments.
v2rayA system-tun remains supported.
TProxy and sing-box TUN are not included in this release.
You can’t perform that action at this time.