The DNS module spoke UDP, TCP and DNS over TLS. An https:// upstream is
now an RFC 8484 POST through an http.Client the upstream keeps between
queries; the TLS handshake is done in the dialer so the server name is
the upstream's hostname while the address dialled is what bootstrap
resolved for it — the module cannot ask itself for its own upstream's
address. A direct upstream dials on a marked socket, as the other
protocols do; a proxied one dials through the xray dispatcher, so the
request leaves through the chosen outbound.
Two things the dispatcher path had wrong for tls:// upstreams: it sent
plain DNS over TCP whatever the protocol, and bootstrap replaced the
hostname by an IP without keeping it, so TLS had nothing to verify
against. The hostname is kept as ServerName on the upstream, the
dispatcher path wraps the connection in TLS for tcp-tls, and the direct
miekg client verifies the same name. The service adds https and tls
hostnames to the bootstrap list, which it skipped for every scheme
address before. CheckDnsUpstream accepts https:// URLs with a host and
still refuses quic://.
Verified on the VM with a raw UDP client against the module, names not
in its cache: https://dns.google/dns-query direct (bootstrap dns.google
→ 8.8.8.8, a v2raya_core connection to 8.8.8.8:443), https://1.1.1.1
/dns-query via proxy (the connection goes to the proxy server's :443),
tls://dns.google via proxy (rewritten to 8.8.8.8:853, TLS verified as
dns.google) and tls://1.1.1.1 direct all answer; the previous rules
restore unchanged. A unit test runs the DoH client against an httptest
TLS server.
The DNS form's placeholder offered https://dns.google/dns-query, the
service turned https:// into protocol "https" and quic:// into "quic",
and the DNS module handed those to a miekg/dns client, which speaks udp,
tcp and tcp-tls only. Saving succeeded and every query on that rule then
failed, visible only in the log.
CheckDnsUpstream in kernel/v2ray accepts an address, tcp://, udp:// and
tls:// (DNS over TLS, which the module does support) and rejects https://
and quic:// with a message that names the alternatives; PutDnsRules
returns it as a 400 before anything is stored. The placeholder in the six
locales shows the supported forms and the docs say which schemes work.
Verified on the VM: https:// and quic:// rules come back BAD_REQUEST with
the message, tls://1.1.1.1 saves and the module logs
addr=1.1.1.1:853 protocol=tcp-tls; the previous rules restore unchanged.
RoutingA could be opened from the dashboard's splitting tile (labelled
"RoutingA"), the proxies page's toolbar ("RoutingA rules"), the settings
row ("RoutingA rules" since the previous commit) and the tutorial. The
label is "RoutingA rules" everywhere it remains, and the proxies page
loses its button: rules are not a property of the node list, and the
dashboard tile that chooses the splitting mode and the settings row are
where a user looks for them.
The lint carried five warnings into every CI run: two unused imports in
AppShell.vue, one in a spec, a let that never changes, and v-html in the
log view, whose input highlight.js escapes.
The templates sat at the end of the syntax reference, behind five
collapsed sections, and the settings row and dialog were titled by the
bare name RoutingA. The dialog header now has a Templates menu next to
the reference button, in two groups: four full rule sets that replace the
rules after a confirmation (China direct; sites outside China through
the proxy; everything through the proxy; only common foreign services
through the proxy) and thirteen additions inserted at the cursor (ads,
streaming, social media, Telegram, AI, developer services, Chinese
endpoints of Apple/Google/Microsoft/Steam, Apple and Microsoft direct,
game platforms, speed tests, LAN, BitTorrent direct, block QUIC). The
reference is a syntax reference again. The settings row and the dialog
are titled "RoutingA rules" in every locale.
Every template uses only v2fly geosite/geoip categories and the three
built-in outbounds; a spec runs each through the editor's checker, and
on the VM each of the seventeen applied through the API while the core
was running.
The app bar's status button carries the spacing to the group button
itself: the class on the OutboundMenu component landed on the menu, not
its activator, so the two sat flush at every width below 1200.
A read of the tree for home-grown code that a dependency or the platform
covers. Each item names what replaces it.
- IPv4 CIDR membership was a binary-string trie (infra/dataStructure/trie)
fed with CIDRs rendered as bit strings; net.IPNet.Contains, which the
same file already used for IPv6, does it. The trie package is gone.
- The response replay cache was an LRU with its own linked list, indexes
and timeout strategy (infra/dataStructure/lru), of which one fixed-size
instance existed; hashicorp/golang-lru/v2, already in go.mod, is that
cache, typed. go mod tidy also dropped go-nanoid, which nothing imported.
- The HTTP client for subscription updates through the local proxy carried
a CONNECT dialer of its own (pkg/util/proxyWithHttp); http.Transport's
Proxy handles socks5:// and http:// URLs, resolves hostnames on the
SOCKS proxy and uses CONNECT for https. Verified on the VM: a
subscription update succeeds in both "pac" and "proxy" modes.
- core/dns/qtype.go listed nine type names in two switches before falling
back to miekg/dns tables that contain the same names; dns.Type.String
and dns.StringToType are the tables.
- The GUI tracked prefers-color-scheme with its own media query and
toggled a theme-dark class nothing reads any more; Vuetify's "system"
theme follows the OS itself. Verified in headless Chrome: auto follows
the OS in both directions, an explicit choice overrides it.
- The AUR packages carried .INSTALL hooks whose only content was a
coloured "Completed!" banner, duplicated in the deb/rpm after-install
scripts; pacman and apt report that themselves. The hooks are gone, the
release workflow stops copying them, and after_install/after_upgrade
keep only daemon-reload and the restart.
- The tap release job downloaded eight artifacts in eight steps;
actions/download-artifact takes a pattern with merge-multiple.
With no subscriptions, the Proxies page showed a card the height of a
screen: a large RSS icon, the import dialog's prompt "Input a subscription
address:" as if it were a caption, and a tonal button in the default
colour that read as disabled. It is now one row on a low surface: the
icon, "No subscriptions yet" with a line on what a subscription does, and
a primary tonal button that opens the import dialog already switched to
Subscription address, so the user does not pick the kind again. The same
button in the dashboard's subscription tile opens that way too; the
Import dialog takes the kind as a prop. The node list's own empty state
said the same wrong prompt and now says what to import.
A source review of the six sections found statements the code does not
support. Corrected: the plain SOCKS and HTTP inbounds always route through
proxy, only the rule port follows the splitting mode; a bare domain()
value is a substring match, domain: is the suffix match; a custom
inbound's RoutingA text takes rules only, default: and outbound: are
ignored and the form's group is the fallback; a DNS rule's localhost is
127.0.0.1:53, and any outbound other than direct goes through the SOCKS
inbound; redirect sends port 53 to the DNS module's 52353 and a busy port
53 is skipped, not fatal; the core hook also gets --v2raya-confdir, and
manual TUN routes are the Configure Route Script setting, not the hook;
pinning a member is the node menu, Edit group changes members; settings
apply on Save and Apply; greatfire is in v2fly's list; a missing geoip
category is "illegal ip rule"; GFWList mode needs Update GFWList first
and downloads from v2rayA/dist-v2ray-rules-dat; rule data is searched in
the XDG data directories; the user unit and the Windows installer log
elsewhere; CORE_START_FAILED also covers a launch failure and the API
timeout; TIMEOUT is a failed TCP connect; registration asks for a 6–32
character password; import needs the kind chosen; port 0 on the API
means random and Port Sharing leaves it on loopback.
Every step of the tutorial links its documentation section. The status
button stops reserving room for the long "Waiting for network" label,
which made it wide on phones; that label widens it only while shown. The
English navigation label reads "Settings", and the two Chinese labels
quoted in the docs get their spaces (更新 GFWList, 开启 IP 转发).
The documentation site's domain has expired and its pages described a
2021 v2rayA. The page now carries its own docs, written against the
current code and shipped with the build, so what a user reads matches the
binary they run: quick start, transparent proxy, routing rules, inbounds
and sharing, flags and environment, troubleshooting. English and
Simplified Chinese; the other locales read the English text and say so.
The sections are Markdown under gui/src/docs/<locale>/, compiled to HTML
at build time by a small vite plugin around marked (a devDependency; the
bundle carries no parser) and loaded on demand, so the first load does not
grow. Headings get ids from their text. The flag table is not written by
hand: GET /api/params reads conf.Params' struct tags (id, short, default,
desc) through reflection, the same tags gonfig parses, and the page renders
it, so a new flag documents itself.
"#docs" and "#docs/<section>" open the page; the RoutingA dialog's help
button, the About page and small book icons in the settings sections and
the inbound dialogs point there instead of at the dead site or the wiki.
The navigation gains a fifth destination.
Each template gets a second action next to Insert: Replace all rules, which
asks for confirmation the way Import does and then swaps the editor content
for the template, default outbound included. Inserting a full template such
as "sites outside China through the proxy" into existing rules left two
default: lines and a mix of both policies; replacing is what a user picking
a policy wants.
The reference panel's last section held the default template and one
ad-blocking line. It now lists eight named templates that cover what people
ask for most: China direct or the reverse, ads, streaming, Telegram, AI
services, the Chinese endpoints of Apple/Google/Microsoft/Steam, and LAN.
Each inserts at the cursor like the other examples.
Only categories from the v2fly geosite.dat and geoip.dat that v2rayA
downloads are used, so a template applies on a stock install: no
Loyalsoldier-only names such as geosite:gfw or geoip:telegram (the core
refuses the config with "illegal domain rule"). Telegram uses the same
address ranges as template_routing.go. Every template routes to proxy,
direct or block, so the save-time check for a connected node in a named
group cannot fail; the description says to rename proxy for a custom group.
Dialogs, menus and tooltips render in .v-overlay-container, which sits
beside .v-application rather than inside it, so they fell back to
Vuetify's Roboto stack. The type family now applies to both roots.
The About text still said "a web GUI client of V2Ray". It now carries
the README's description (own Xray-based core, transparent proxy on the
three platforms, the protocols it speaks), the founder line the
maintainers asked for — 由 @mzz2017 创立 — and the local-data note, in
all six locales.
Its label changes between 就绪, 正在运行 and the hover text (启动/关闭),
so the group selector beside it moved every time and the two ended up
touching. Every label the button can show is laid out in the same grid
cell, visible or not, and the button takes the widest.
Both outbound chips were tonal and, on the default seed, the same
beige; the text view colours the outbound. A direct rule's chip is
outlined and neutral, a proxied one tonal in the primary colour, block
stays red.
The login bootstrap retried only network errors; a timeout or an HTTP
error on the first request returned without a dialog, a notice or a way
back short of reloading. Timeouts are retried like network errors, and
when the retries are spent a banner names the address and carries a
retry.
A settings save the backend rejected kept the rejected values in the
form, so the next save resent them; the form reloads what is stored.
The "members only" chip on the proxies page was not focusable. A
WebSocket frame that is not JSON threw inside the handler.
Keeping every stored field of a rule also kept upstream and domain, the
migrated aliases of server and domains that the generator prefers, so
an edit to the visible fields did not reach the running configuration.
The aliases fold into the form and are not sent back. The two SSR-only
locale keys are gone.
After a start from the app bar the confirmed state came from a touch,
but only its running flag was read: a core whose network is paused was
shown as running. The state is derived the way the dashboard derives
it.
ShadowsocksR is no longer supported by the service; the editor has no
SSR tab and the share-link codec no longer knows the scheme. A stored
node the service still lists cannot be opened for editing, which the
editor reports and closes.
The WireGuard form had DNS and Endpoint inputs that no share link and
no backend field carries, while workers, reserved and kernelMode —
which the backend parses and exports — were dropped on every edit. The
form now has the three real fields and the codec round-trips them.
When a node's link could not be loaded, the editor stayed open on a
default VMess model; saving replaced the node the user meant to edit.
The dialog now closes with the error.
The action rows on the settings page (RoutingA, ports, DNS, custom
inbounds, TUN, About) were list items with a click handler but no link
role, so they took no focus and Enter did nothing. They are links now.
The DNS dialog rebuilt each rule from its three editable fields, so a
save dropped the matchers the DNS module reads and only the API sets
(ip, queryType, clientIP, action, policy). The rows keep every field
they came with.
The log stream kept every line since the page opened; it keeps the last
20000. The GFWList hint condition was named as if it meant stale; it
means the local file's date is ahead of the remote one, which is what
the text explains.
The dashboard's touch rows do not carry a subscription server's index,
so the member dialog keyed every subscription row as subscription 0: a
member of the second subscription showed unchecked, nodes with the same
id in two subscriptions shared one checkbox, and Save re-pointed every
chosen node at the first subscription's node with that id.
Three service packages outside the executable's dependency graph
(common/antiPollution, pkg/util/gopeed, kernel/vmessInfo), a blank
import of miekg/dns the core already imports, the --core-type flag no
code read, the PutAccount handler whose route was commented out, two GUI
API wrappers without a caller, two .SRCINFO files the release regenerates
and an unreferenced runit sample. The workflow path filters watched a
root go.mod that does not exist and the PR build skipped core/.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The card header put the server name, the subscription name and the group tag
on one flex row: a long tag such as "PROXY - 负载均衡 (2)" squeezed the name
into two lines while staying centred against them, and the subscription name
wrapped wherever the row broke. Bulma's small message also pads the header
and the body differently, so a gap opened under the title and the body text
sat a step further in.
The name takes the row, a tag that does not fit drops to its own line, the
subscription name always sits under both, and header and body share their
padding.
The card asked for 65rem. The root font is 0.9em up to 1400px and 16px above
it, so on any wider viewport — a 200% display scaling or a zoomed-out window
gets there — 65rem is 1040px while the wrapper Buefy sizes the dialog with is
capped at 960px: the card ran 80px past it and the close button, which sits on
the wrapper's corner, ended up in the middle of the header. 60rem is 960px at
the 16px root and never wider than the wrapper.