TGE v1.2.6

TGE v1.2.6

This patch release completes the Runovel repository standardization and fixes Linux installer execution in clean Git checkouts.

Fixed

• Preserved the executable Git mode of deploy.sh, ensuring direct installer execution works correctly after a clean Linux checkout.

Added

• Runovel governance and contribution documentation.
• Security reporting guidance and private vulnerability reporting support.
• CODEOWNERS, issue templates, and pull request template.
• GitHub Actions shell and repository bridge validation.

Changed

• Standardized the canonical repository identity as runovelhq/tge.
• Renamed the Apache 2.0 license file to LICENSE without changing its content.
• Preserved existing installation, upgrade, and bridge compatibility.

Validation

• Shell syntax validation passed.
• Clean Linux checkout validation passed.
• All 102 repository bridge checks passed locally and in GitHub Actions.

Upgrade

Existing TGE installations may continue using the established upgrade process:

sudo tge upgrade

No configuration migration is required for this release.

v1.2.5

Highlights

• Adds the Runovel migration bridge for the transition to the organization repository.
• Preserves repository compatibility for existing and future installations.
• Incorporates completed disposable runtime validation.
• Hardens upgrade source, version, and temporary-directory validation.
• Makes configuration backups fail closed before upgrades continue.

Migration Notice

This is the final bridge release before repository migration. Future development will continue under:

runovelhq/tge

Existing installations remain supported through the compatibility bridge.

Compatibility

• Legacy repository resolution is retained.
• Repository migration support is included.
• Canonical CLI installation validation is enforced.
• Backup handling fails closed.
• Upgrade validation is improved.

Validation

• Disposable runtime validation completed.
• Repository bridge tests passed.
• Migration compatibility verified.

Known Limitations

• Repository standardization has not yet been applied.
• Runovel repository files will be added after transfer.
• Legacy compatibility references intentionally remain for migration.

v1.2.4

Add automatic MASQUERADE for upstream gateway-originated health-check probes in server_gateway mode, enabling FortiGate SD-WAN health checks without source-specific gateway configuration.

v1.2.3

Add stateful server-side MASQUERADE to server_gateway mode, matching the v2rayA and WireGuard forwarding model and removing upstream source-routing and RPF requirements.

v1.2.2

Fix server_gateway forwarding to use the host main default route, remove stale tunnel policy rules, disable ICMP redirects, and improve health checks and logs.

v1.2.0

V2rayTGE v1.2.0

Added

• Added server_gateway egress mode.

  • Traffic entering from GRE/direct edge can now bypass tun0/wg0.
  • The v2ray policy table can route traffic directly through the server gateway.
  • No server-side NAT is added in this mode; NAT/PBR remains on FortiGate or the edge device.

• Added version-aware CLI dashboard.

  • Shows installed version.
  • Checks latest GitHub release/tag.
  • Shows upgrade status.

• Added configuration editor.

  • New menu option: Edit Egress System Configuration.
  • Allows editing saved config values one by one without rerunning the full wizard.
  • Creates a backup before each saved edit.
  • Can apply saved configuration directly from the editor.

• Added in-app upgrade flow.

  • New menu option: Upgrade Egress System.
  • Downloads the latest GitHub release/tag.
  • Preserves existing /opt/v2raytge/config.env.
  • Creates a pre-upgrade backup automatically.
  • Uses release/tag raw URLs to avoid accidentally reinstalling main.

• Added backup and restore.

  • New menu option: Backup / Restore Config.
  • Backups are stored in /var/backups/v2raytge.
  • Restore flow creates a pre-restore backup before overwriting config.

• Added root VERSION file.

  • Installed systems now read /opt/v2raytge/VERSION first.
  • meta.env remains as fallback metadata.

Changed

• Updated main CLI menu layout.
• Updated deploy.sh so REPO_RAW and GH_REPO can be overridden during tagged upgrades.
• Updated documentation for the new menu, upgrade, backup/restore, and release versioning behavior.

Notes

Before publishing this release, make sure the root VERSION file matches the GitHub tag, for example:

v1.2.0

v1.1.0 - WireGuard Egress Backend

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.

V1.0.1-Stable

• GRE tunnel integration
• Policy-based routing table
• NAT rules finalized
• No traffic drop during reload
• Systemd service integrated
• Wizard setup