2077 Commits
Author SHA1 Message Date
Markson Hon 2303ad9a3d Merge pull request #1997 from Zakkaus/gui-md3-pr v2.5.0 2026-09-19 21:21:26 +08:00
Zakk 7ab8b690e1 docs: the README shows the new dashboard and the RoutingA editor, light and dark in one image 2026-09-19 23:17:06 +10:00
Zakk ce771911b5 chore(gui): the Buefy and Bulma GUI is gone
App.vue, the node page, every modal, the Vuex store, the axios and
Buefy plugins, the SCSS and the helper scripts of the old GUI are
deleted; nothing imports them and no dependency of theirs remains.
2026-09-19 23:17:06 +10:00
Zakk 041d356c9f i18n(gui): six locales for the rewrite, with plural forms for counts 2026-09-19 23:17:06 +10:00
Zakk 206c51c148 feat(gui): the pages — dashboard tiles, proxies, settings, logs, about
The dashboard is a grid of single-purpose tiles: the core, live speed
with totals, the node in use with a member picker and a group editor,
the transparent proxy and its implementation, the splitting mode with
RoutingA and the ports a click away, the members' latency measured on
arrival, the subscriptions. The proxies page holds subscriptions, nodes
in cards or a list with select-all and batch actions, groups, the node
in use, latency tests and the splitting rules. Settings is one form
with a save bar; logs a virtual list with filters and search.
2026-09-19 23:17:05 +10:00
Zakk 3841a1e7e6 feat(gui): every dialog on Vuetify
Login, import, sharing, subscription, outbound group, the node editor
with a protocol select and one form per protocol (twelve), the settings
dialogs (GFWList, domains excluded, whitelist IPs, TUN processes and
route script, DNS rules as cards, RoutingA with a code editor, a form
view, a syntax reference and import/export, ports, custom inbounds),
the subscription update settings and the onboarding tutorial.
2026-09-19 23:17:05 +10:00
Zakk eb27dc8981 feat(gui): the Material shell — drawer, rail and bottom bar, app bar, page header, hosts
Four destinations (dashboard, proxies, settings, logs) in a standard
drawer from 1200 px, a rail below, a navigation bar on phones; the core
state and the group chip in every header; theme, language and account
menus; the theme panel with seed swatches and a hue slider; hosts for
banners, snackbars, dialogs and the loading bar; the traffic plot.
2026-09-19 23:17:05 +10:00
Zakk 89fb7d87b1 feat(gui): the spine — typed API, session, store, composables, theme
The backend's calls in one typed module with a session-scoped client
(a reset aborts every request, a 401 ends the session, a busy backend is
asked again for a read); the Pinia store; composables for dialogs,
notices, banners, loading, the message socket, the traffic ring buffer,
the log stream and outbound groups; the share-link codec moved from the
old editor; the Material 3 theme derived from a seed colour (tonal
spot, monochrome for colourless seeds), the type scale and the
component overrides.
2026-09-19 23:17:05 +10:00
Zakk 0daa826396 build(gui): Vuetify 4, TypeScript, Pinia, vue-i18n 11 in composition mode, Vitest, a PWA
The toolchain of the rewrite: Vite with vite-plugin-pwa (autoUpdate,
/api/ never cached), vue-tsc, ESLint's flat config, Vitest with
happy-dom and a mount helper, an i18n check and a gzip size gate in CI,
Red Hat Text self-hosted under /static/fonts.
2026-09-19 23:17:05 +10:00
Zakk d41ebec2d6 feat(service): /version reports the core's own version 2026-09-19 23:17:05 +10:00
Zakk 86eaaee6b5 feat(service): traffic frames on the message socket
The core's StatsService is registered and enabled in the template;
a producer reads the inbound counters every second and publishes
{up, down, upTotal, downTotal} as a traffic frame, which the GUI's
dashboard plots. A GUI that does not know the frame type ignores it.
2026-09-19 23:17:05 +10:00
Zakk 868497a0e9 feat(service): a group may route through one selected member
An outbound group with several members is balanced by the observatory
(least ping). The group's setting now also names one member's share
link as Selected: the core template then keeps only that member, the
touch flags it on the connected entry, and PUT /outboundSelection sets
or clears it. A selection that matches no member is ignored, so a node
removed or renamed by a subscription update returns the group to
balancing instead of breaking it.
2026-09-19 23:17:05 +10:00
Markson Hon 6cc6112831 Merge pull request #1996 from Zakkaus/service-scan-fixes 2026-09-19 21:14:59 +08:00
Markson Hon 00fbd01c7a Merge pull request #1994 from Zakkaus/gui-vue3 2026-09-19 21:14:44 +08:00
Markson Hon 4ee373cd3c Merge pull request #1995 from v2rayA/main
fix(core): re-add missing xray core version number
v2.4.25
2026-09-19 20:04:25 +08:00
Zakk 6f7895f477 fix(jwt): read the uname claim the login issues
The middleware looked up name, so the request's identity was always
empty.
2026-09-19 22:04:12 +10:00
Zakk b232abde47 fix(reqCache): a request id's lock is dropped once its last user leaves
The map gained one mutex per request id and never shrank; the GUI sends
a fresh id per request.
2026-09-19 22:04:12 +10:00
Zakk d66c3927a5 fix(server): requests that change state apply or restore; requests that fetch have deadlines
PUT /dnsRules regenerates the running core's config and restores the
previous rules when that fails; SetPorts restores the previous ports
when the restart fails. The HTTP latency test drops subscription
entries as intended. The remote GFWList version request has a deadline
and its cache a one-hour TTL. CheckUpdate picks the index of the running
architecture and closes the body on every path.
2026-09-19 22:04:11 +10:00
Zakk 7c482856c8 fix(kernel): races and leaks around the core process and the observatory
Running() reads the process under the manager's lock; the early-exit
flag is atomic; a second Close no longer waits on the reaped process; an
empty log chunk no longer panics. The observatory producer rejects tags
it cannot map instead of attributing them to the first node, paces every
path so an unknown tag cannot spin it, closes an unavailable connection
before dropping it and cancels each dial context at once. Balancer
outbounds get their serverInfoMap entry on success, not only on failure.
The resolv hijacker is serialised between the start path and the
connectivity monitor.
2026-09-19 22:04:03 +10:00
Zakk d30f94cc38 fix(configure): reverse every type group when deleting; a refused ping is not a latency
SortSameTypeReverse only reversed the first type group, so DeleteWhich
processed subscriptions front to back and its index shifting pointed
later connected entries at the wrong subscription. Ping treated a
connection refusal as a measured latency. GetLenSubscriptionServers
exited the process on a lookup error where its siblings panic and the
handler recovers.
2026-09-19 22:04:03 +10:00
Markson GuGa Beyond 1da93f75a9 fix(core): re-add missing xray core version number 2026-09-19 19:59:27 +08:00
Zakk 71070a4301 style(gui): Bulma 1 renders the 0.9 metrics and palette
Bulma 1 tints the neutral scale with the scheme hue, derives button text
from lightness, drops the button border and the card head's bottom rule,
pads the modal card wider, uses Inter and a larger radius. Measured
against the previous build on the settings dialog and the node table in
both themes, every computed value now matches: the neutral scale is
registered with zero saturation, the legacy primary/link values are kept,
button weight, label weight, modal widths and paddings are set through the
Sass module's variables (Bulma 1 re-registers them per component, so a
:root override does not reach them), the invert lightness of the palette
colours is pinned to white, radius and the system font stack are restored
on :root, and the button geometry and the primary button's translucent
text are written as rules where Bulma 1 has no variable for them.
2026-09-19 15:36:44 +10:00
Zakk 619510552f refactor(gui): dialogs close by event, state crosses app instances through the store
Buefy 3 mounts every programmatic dialog, loading overlay and snackbar in
its own application, and Vue 3 no longer skips abstract components when
resolving $parent, so a dialog's $parent is the transition around it:
$parent.close() throws, and $parent.$parent.runningState no longer reaches
App. This commit moves those seams onto explicit contracts:

- Every dialog closes with $emit("close"). Buefy's Modal listens for it on
  a programmatic component; the inline b-modal hosts in App.vue, node.vue
  and modalCustomPorts.vue listen for it on their child. The card head
  gets a Bulma .delete button for it, and the library's own corner button
  is off (defaultModalCanCancel); the About dialog, whose content is raw
  HTML, gets the same button wired by hand after it renders.
- Every component declares its emits. Without the declaration Vue 3 also
  passes the listener through to the root element, so <node-list @input>
  received every native input event bubbling out of the node page and
  overwrote App's running state with an Event.
- The two dialogs that changed the navbar's running text through
  $parent.$parent now commit RUNNING to the store; App watches the store
  field into its data and mirrors the data back, so the data stays the
  source of truth and a repeated commit is still a change.
- session.js registers every programmatic instance that outlives
  app.unmount() — modal and loading handles through openModal/openLoading,
  snackbars in axios.js — and restart() closes them first; instances that
  closed themselves are dropped on the next registration. Buefy 3 exports
  SnackbarProgrammatic and friends as classes bound to an app, so
  module-level code takes the root app's $buefy instead of calling the
  class. loading.open() reads options.onClose on close, so the wrapper
  always passes an options object; b-loading takes model-value, not
  active.
- b-message declares a click event it never emits, so the sidebar cards'
  click moved to a wrapping element.
- CusBInput, a 2019 copy of Buefy's Input, is gone; the three number
  inputs are b-input, which has the same v-model and checkHtml5Validity.
- The node table component is NodeList (vue/multi-word-component-names),
  and the v-html in the user menu sits on a span rather than the item
  component.
- Buefy 3 pins the table sort icon to the header cell's right edge, over a
  short label; it goes back after the label. The head's close glyph is
  drawn in the text colour like the old corner button was.
2026-09-19 15:36:44 +10:00
Zakk e06598542d refactor(gui): templates in Vue 3 and Buefy 3 syntax
Vue 3 removes .sync, the slot and slot-scope attributes, the .native
modifier, filters and the value/input contract for v-model on components;
Buefy 3 renames its two-way props to modelValue and no longer emits input
from Select, Switch and Tabs. Nothing here changes what a template
renders or sends:

- b-modal :active.sync -> v-model; b-table :checked-rows.sync and
  :current-page.sync -> v-model:checked-rows / v-model:current-page;
  b-sidebar :open -> :model-value.
- slot="…" -> <template #…>; the three <div slot="trigger" slot-scope>
  are wrapped in a template, as # only goes on templates and components.
- @event.native -> @event, which Buefy 3 passes through to the root
  element; b-tag declares its own click that fires on the inner span
  only, so the status tags' handlers moved to a wrapping span to keep
  the whole tag clickable.
- b-select / b-switch / b-tabs @input -> @update:model-value.
- <node v-model="runningState"> -> @input, since Vue 3 compiles v-model
  on a component to update:modelValue and node.vue emits input.
- beforeDestroy/destroyed -> beforeUnmount/unmounted; the unix2datetime
  filter is a method; $set is a plain assignment.
- highlightLog renders with h(); parent: this is dropped from the
  programmatic modal calls — Buefy 3 spreads every parameter into the
  Modal props and the unknown one aborted the mount.
- b-message :active="true" was a dead attribute.
2026-09-19 15:36:44 +10:00
Zakk 9848c38894 build(gui): Vue 3, Buefy 3, Bulma 1, Vuex 4, vue-i18n 9 and the session module
Vue 2 has been out of support since the end of 2023, and every library
the GUI sits on is pinned to it: Buefy 0.9, Vuex 3, vue-i18n 8,
vue-virtual-scroller 1, @vitejs/plugin-vue2. This commit swaps the
toolchain; the templates still carry Vue 2 syntax (.sync, slot,
slot-scope, .native) and the build fails on them until the next commit.

- buefy 3.1 is the official Vue 3 release and depends on Bulma 1, so
  buefy.scss is rewritten as `@use "bulma/sass" with (...)`, keeping the
  same colour values; Bulma 1 needs Dart Sass >= 1.79 for color.channel,
  hence sass ^1.86. The danger colour's 0.73 alpha, which Bulma 1 drops,
  is restored on the CSS variable.
- The root instance is built by plugins/session.js. Its restart() replaces
  $remount: Vue 3 has no $children to walk, and Buefy 3 mounts each
  programmatic dialog in its own application, so restart() closes the
  registered handles, unmounts the root (whose beforeUnmount hooks close
  the WebSocket and the matchMedia listener) and mounts a new one.
  Components keep calling this.$remount(); it is set as a global property
  from session.js rather than imported by the tree, which would be a
  circular import.
- axios, dayjs and the Buefy toast register on the application instead of
  Vue.prototype; module-level code uses i18n.global, the legacy instance
  no longer exposes t() directly.
2026-09-19 15:07:40 +10:00
Markson Hon 2602b25ee0 Merge pull request #1992 from Zakkaus/tun-core
feat(service): the tun transparent proxy is the core's own device; TinyTun removed
v2.4.24
2026-09-19 12:27:21 +08:00
Markson Hon 3d78a6faf7 Merge pull request #1991 from Zakkaus/tun-core-core
feat(core): tun-mips, a TUN inbound on mipstack, and DNS-module egress binding
2026-09-19 12:27:06 +08:00
Markson Hon d0c80a017f Merge pull request #1993 from Zakkaus/fix-ico
fix(gui): the favicon carries 16, 32, 48 and 256 px again
2026-09-19 08:49:03 +08:00
Zakk 679e4c28a1 fix(gui): the favicon carries 16, 32, 48 and 256 px again
b1fd2c12 said it rendered a multi-size .ico from the SVG, but the file it
committed holds a single 16x16 entry (664 bytes): the packer was fed one
size. Browsers that pick the .ico over the SVG (bookmarks, some tab
strips, pinned sites) scaled 16 px up. Before that commit the file was one
32 px entry.

Rebuilt from gui/src/assets/img/v2raya-icon.svg with rsvg-convert as
16, 32, 48 and 256 px PNG entries (18 KB). The installer icon stays as
107d8e35 set it.
2026-09-19 10:37:21 +10:00
Zakk e05e672fe5 build: drop the tinytun build tag and ship Wintun from its own package
The binaries workflow, the PR workflow and build.ps1 no longer pass
-tags tinytun; there is nothing behind the tag. The Windows installer
takes wintun.dll from the official 0.14.1 package, pinned by hash, one
DLL per architecture, and deletes a tinytun.exe an earlier installer left
in the application's bin directory. The README states what the built-in
TUN does and its known limitation on Windows and macOS.
2026-09-19 10:34:56 +10:00
Zakk 6a85f46641 feat(gui): tun is the built-in TUN; drop the TinyTun-only controls
The transparent-proxy option reads "tun" and is enabled by the version
endpoint's tunSupported flag. The bypassed-interfaces picker and the
process-exclusion backend selector go away with the settings behind them;
the interface-list fetch and its state go with the picker. The route
script and process exclusion dialogs stay, renamed, with copy that no
longer refers to a TinyTun process; the tooltips describe what the
built-in TUN does and its known limitation on Windows and macOS. The log
viewer no longer classifies a [tinytun] source. All six locales updated;
every removed key has no remaining reference.
2026-09-19 10:34:56 +10:00
Zakk 2d95891aed feat(service): tun routes and system DNS on Windows and macOS
Neither platform has a socket mark, so the physical default route is left
in place and two /1 routes per family are added on the TUN instead; the
core's sockets and the DNS module's upstreams are bound to the physical
interface, which the template reads from the default route before the
TUN routes exist.

Windows points the adapter's DNS at the TUN gateway address with the
lowest interface metric; queries sent there enter the TUN and the core
relays them to the DNS module. macOS needs two things more. A socket
bound to en0 with IP_BOUND_IF looks routes up in en0's scope, and once
the /1 routes exist the only match is theirs, so the lookup fails with
ENETUNREACH: a scoped copy of the physical default route
(route add -ifscope en0 default <gw>) gives bound sockets a way out. And
mDNSResponder scopes its queries to the service's interface, dropping a
reply that arrives through the utun, so the system resolver is pointed at
loopback and the DNS module gets a 127.0.0.1:53 listener in tun mode.
The routes use the gateway form, as xray's own tun does. The kernel
assigns the utun unit and the service finds the device by its address;
the previous resolvers of every network service are kept for stop.

Both were exercised in milestone C: a Windows Server 2025 VM and an
arm64 MacBook. Applications that query a LAN resolver directly still
bypass the TUN on these platforms in this phase; that is documented as a
known limitation.
2026-09-19 10:34:56 +10:00
Zakk 88841d7d9d fix(core): DNS module answers match the client's EDNS
The module asked every upstream with DNSSEC OK and handed the upstream's
additional section back untouched, so a client got an OPT record it never
sent — carrying the module's loop token and the DO flag — and RRSIG
records it did not ask for. macOS's resolver treats such an answer as
invalid and waits out its 30-second timeout on every uncached name, which
made the tun mode's loopback resolver unusable there. Upstream queries no
longer set DO (the module validates nothing), and the response is
rewritten to the client's EDNS: no OPT when the client sent none, a fresh
OPT with the client's UDP size and DO bit when it did, and RRSIGs only for
a DO client.
2026-09-19 10:34:55 +10:00
Zakk 1dd2bf28ad feat(service): the tun transparent proxy is the core's own device
transparentType=tun no longer starts the TinyTun process. The template
emits a tun-mips inbound tagged transparent — device name, address, MTU,
the DNS module's address as the relay target, the user's exclusion list
plus v2rayA and the core by name and v2rayA by PID — and the service does
what the operating system needs once the core has the device up.

On Linux that is one table and four policy rules: table 2020 holds the
default route into tun0; marked packets (0x80: the core's sockets, the
direct outbound, the DNS module's upstreams) look up main in full and
leave through the physical interface, or fail with ENETUNREACH when main
has no route for their family rather than fall into the TUN; unmarked
packets take main with its default route suppressed, so LAN and static
routes stay physical, and everything else goes to table 2020. The main
table is never edited, so stopping restores egress by itself. A rule in
our preference range or a route in our table that is not ours is reported
and left alone; our own leftovers from a crash are removed first. Every
command that succeeded is recorded and undone in reverse on stop.

Three things the TinyTun path never hit are now on tun's path, so they
are fixed here: the DNS module is generated in tun mode (TinyTun did DNS
itself); its 127.2.0.17:53 listener is only added when port 53 is free,
instead of making the core exit on a host running another resolver; its
primary listener stays on loopback unless port sharing is on or the user
chose an address, and the DNS REDIRECT rules and their cleanup follow the
module's port instead of a hard-coded 52353, and a ::1 listener is added
when IPv6 is supported, because ip6tables REDIRECT delivers an
application's IPv6 query to ::1 which the IPv4 listener never saw. The
tun branch no longer
skips those rules: they are what catches queries to a LAN resolver, which
the routing keeps off the TUN.

The connectivity monitor probes the core's API port; the TinyTun socks
loop-back port it used is gone. Removed with TinyTun: --tinytun-bin, the
tunProcessBackend (eBPF) and tunBypassInterfaces settings (connected and
static routes bypass the TUN unconditionally now), the /networkInterfaces
endpoint that only served the latter, and the build tag. The version
endpoint reports tunSupported instead of tinytunSupported.

Tests cover the generated inbound and DNS module, the listen-address
rules, the redirect port, and — with V2RAYA_CORE_BIN set — that the
generated document loads in the real core. Windows and macOS route
handling follows in a separate commit; until then those builds report
the TUN as unsupported.
2026-09-19 10:34:55 +10:00
Zakk a6c2d5f1d2 feat(core): bind the DNS module's own sockets to an egress interface
On Linux the module's upstream, bootstrap and health-check sockets carry
SO_MARK 0x80, which the transparent-proxy rules exempt. Windows and macOS
have no mark: once a TUN holds the default route, those sockets would send
the module's own queries into the TUN, where the core's port-53
interception hands them straight back to the module. The module config
gains egress_interface; when set, every dialer created by
newMarkedDnsClient binds to it with IP_UNICAST_IF / IPV6_UNICAST_IF on
Windows and IP_BOUND_IF / IPV6_BOUND_IF on macOS. Unset, the dialers are
unchanged, and Linux keeps the mark.

The darwin and windows tests dial through the dialer and read the option
back; they run on those platforms. The interface lookup itself is tested
everywhere.
2026-09-19 10:34:55 +10:00
Zakk fa051aa35f feat(core): register the tun-mips inbound and load it from JSON
The inbound is registered like xray's tun: it declares no listening
network, opens its device in Start, and tears the stack down in Close. Its
settings object is validated on load — name, mtu, address4 and dnsTarget
are required, address6, excludeProcesses, selfPids and directTag are
optional — so a field the service forgot fails the configuration instead
of becoming a zero value at runtime.

The JSON loader gains an inbound side. It is a separate protocol set from
the outbound one, and a protocol used in the wrong direction is an error
rather than being stripped and then silently skipped. The three production
entry points (file builder, cmdarg loader, reader loader) now share one
strip and one append step, so an inbound cannot be handled on one path
and forgotten on another. The receiver settings carry the sniffing block,
which is what the proxyman builds the sniffing context from.

Tests load the document the service will generate through both the file
and the reader path and check tag, sniffing, every settings field, no
listening port, and that the native socks inbound beside it is untouched;
they reject tun-mips as an outbound and anytls as an inbound, fail a
document missing dnsTarget, and confirm a document without custom
protocols is returned byte-identical.
2026-09-19 10:34:55 +10:00
Zakk 834d8dd340 feat(core): tunmips process exclusion by socket owner
A flow's owner is looked up once per TCP connection or UDP session from
the application's local address and port: sock_diag plus a /proc fd scan
on Linux, the iphlpapi owner-PID tables on Windows, the pcblist sysctl on
macOS. A wildcard-bound UDP socket is matched by port when no exact match
exists. When any owner is the core or v2rayA itself (by PID, so a renamed
binary still counts) or is on the user's list (by executable basename,
case-folded and without ".exe" on Windows), the session is dispatched with
a forced outbound tag so the router is skipped and the direct outbound —
which already carries the self-exclusion mark — takes it.

An owner that cannot be determined, because the lookup failed or the
socket is already gone, leaves the flow on its normal route: proxying a
packet that should have gone direct is the safer mistake, and this is the
same boundary TinyTun's /proc backend had. The Windows and macOS lookups
compile but are verified on those machines, not here.
2026-09-19 10:34:55 +10:00
Zakk 247531c81c feat(core): tunmips answers port-53 flows through the DNS module
A query the application sends to any resolver that is not an address of
this host — a public one, the TUN gateway address the system resolver is
pointed at on Windows and macOS — is relayed to the core's DNS module
instead of being routed. UDP sessions are per four-tuple and replies are
sourced from the resolver the application queried; TCP streams are relayed
both ways. Queries to loopback or to one of the host's own addresses are
left to ordinary routing: they never enter the TUN in the first place, and
the module's own listener on 127.2.0.17 is one of them.

The relay target is the module's listen address; it is not yet wired to
configuration, which the inbound registration commit does.
2026-09-19 10:34:55 +10:00
Zakk b4472b0e33 feat(core): tunmips forwarder hands TCP and UDP flows to the dispatcher
Each accepted TCP connection becomes one DispatchLink with the same session
context xray's tun inbound builds (inbound tag, sniffing request, user
level, access log), so routing rules, geosite and sniffing treat TUN
traffic exactly like the socks inbound did.

UDP is keyed by the application's source address only: datagrams from one
socket to any number of remotes share one dispatcher session, every buffer
read by the outbound carries its own destination in buf.Buffer.UDP, and
every buffer the outbound writes back carries the remote it came from,
which the stack uses as the source address of the datagram it sends to the
application. That is the full-cone behaviour TinyTun's socks loop could
not offer. The datagram is enqueued under the session lock because the
session is closed under the same lock when the outbound finishes.

Tests use a fake dispatcher: one TCP flow yields one DispatchLink with the
right destination and inbound tag and bytes flow both ways; two UDP
destinations from one source yield one session whose buffers carry each
destination, a packet from a third remote is written back with that
remote as its source, and the session is recreated after the outbound
finishes.
2026-09-19 10:34:55 +10:00
Zakk aaf18bd645 feat(core): tunmips device and stack skeleton for the in-core TUN
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.
2026-09-19 10:34:55 +10:00
Markson GuGa Beyond 447e43cf07 fix(dir): remove old core/xray submodule dir v2.4.23 2026-09-19 07:07:24 +08:00
Markson GuGa Beyond 107d8e35d3 fix(ico): re-added hidpi icon 2026-09-19 07:02:09 +08:00
Markson Hon 648c7e3b20 Merge pull request #1990 from v2rayA/dependabot/npm_and_yarn/gui/flatted-3.4.4
build(deps): bump flatted from 3.2.7 to 3.4.4 in /gui
2026-09-18 20:16:28 +08:00
dependabot[bot] cd8fc07b28 build(deps): bump flatted from 3.2.7 to 3.4.4 in /gui
Bumps [flatted](https://github.com/WebReflection/flatted) from 3.2.7 to 3.4.4.
- [Commits](https://github.com/WebReflection/flatted/compare/v3.2.7...v3.4.4)

---
updated-dependencies:
- dependency-name: flatted
  dependency-version: 3.4.4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
2026-09-18 12:06:02 +00:00
Markson Hon 98184ed7cb Merge pull request #1988 from Zakkaus/vite6
build(gui): bump vite from 4.5.14 to 6.4.3, with the define it rejects replaced
2026-09-18 20:04:52 +08:00
Zakk 9e0f73ee7b build(gui): bump vite from 4.5.14 to 6.4.3, with the define it rejects replaced
Dependabot's bump fails the build: vite.config.js defined the global apiRoot
as a template literal evaluated on every read (the backend address lives in
localStorage and the address dialog changes it), and Vite 5+ only accepts a
literal in define. The global is a getter on window now, installed by a plugin
imported first in main.js, returning the same expression on every read; the
call sites are untouched.
2026-09-18 21:33:27 +10:00
Markson Hon 4f8a83b0ff Merge pull request #1984 from Zakkaus/subscription-status
fix(subscription): show the usage once; tidy the header and the sidebar handle
v2.4.22
2026-09-18 14:21:23 +08:00
Markson Hon 872d5621d0 Merge pull request #1985 from Zakkaus/log-modal-width
fix(gui): keep the log dialog's close button on the card at wide viewports
2026-09-18 14:21:06 +08:00
Markson Hon 126ecd0ebb Merge pull request #1986 from Zakkaus/sidebar-cards
fix(gui): lay out the status sidebar cards evenly
2026-09-18 14:20:56 +08:00
Markson Hon b89545ac78 Merge pull request #1983 from Zakkaus/grpc-x-net
fix(deps): bump grpc so the service builds against x/net 0.54
2026-09-18 14:20:42 +08:00