getsockopt(IP_UNICAST_IF) hands the interface index back in host order while
setsockopt wants it in network byte order, so the second swap in
boundProbeInterface compared 0x01000000 against 1 and the IPv4 cases of
TestBoundDirectDialerSocketOptions failed on Windows.
Revision of the dashboard probe: the UDP fallback used an unmarked, unbound
socket, so its datagram entered the transparent interception the probe is
meant to stay out of and the round trip measured the local stack. Take the
dialer PingWithDialer was given, as the TCP dial already does.
Every core the service starts has outbound traffic counters on, and with them on
xray wraps the underlay connection of a native QUIC outbound in a
*stat.CounterConnection. That wrapper embeds net.Conn alone, so ReadFrom and
WriteTo are hidden and hint/proxy/juicity and hint/proxy/tuic failed their
net.PacketConn assertion before a single QUIC packet left: the node imported, and
then every connection through it died on the spot. Unwrap the stats connection
before the assertion.
A QUIC server listens on UDP only, so the TCP dial the ping made to its port said
nothing and every juicity, tuic and hysteria2 node read TIMEOUT. Keep the TCP
attempt, and when it fails ask the same port over UDP with a QUIC long header
carrying a reserved greased version: a QUIC server answers that with a Version
Negotiation packet (RFC 9000 section 6), and the round trip of that answer is the
latency. A node that answers neither probe is still TIMEOUT; the troubleshooting
pages in the six locales describe that.
Move default: proxy back to the first line so RoutingA.vue treats russia as a replacement, not a snippet. Fix presets.spec.ts to match geosite:category-ru. Remove copyright header per review.
Added rules for youtube, telegram, google - etc - services taht might still operate on .ru and on ru-geoip / geosites.
Signed-off-by: Mishalski <100153948+wywywywycloud@users.noreply.github.com>
The iptables path wrote each whitelisted CIDR with its own iptables
process. With the mainland China group (about 15,000 CIDRs) a core start
spent minutes on this, and every packet of a direct connection walked
the list linearly.
Load each family into one hash:net set with a single `ipset restore` and
match it with one rule at the old position. Without ipset, write the
rules with one `iptables-restore --noflush` per family; without that,
keep the per-rule commands. Cleanup destroys the sets.
A Shadowsocks link with a stream cipher (rc4-md5, aes-128-cfb, aes-256-cfb,
chacha20-ietf) or with none/plain imported without complaint and failed at
core start with "unknown cipher method", so the user saw a broken core rather
than a refused node. xray-core dropped the stream ciphers in 2021 and never
took none or plain in the shadowsocks outbound; these are also the ciphers
ShadowsocksR providers hand out.
ParseSSURL now refuses them with LINK_UNSUPPORTED_CIPHER, which NewFromLink
passes through instead of calling the link malformed; subscriptions skip such
nodes with a warning as they skip other unparseable ones, and the Clash
importer goes through the same parser. The node form drops none and plain and
offers xchacha20-ietf-poly1305, which the core does accept. The six locales
carry the message, and the quick-start pages say which ciphers work.
The repository had six markdown issue templates, no pull request template and
no guide, so a report rarely said which version it was and a pull request
rarely said what its author had run.
The issue templates become four GitHub forms, English and Chinese kept apart,
asking for the version and why it is not the latest, the system and install
method, the transparent proxy mode, the steps, the logs and the person who
answers for the report. Usage questions go to Discussions through config.yml,
and blank issues are off. The pull request template, also in two languages,
asks for the change in the author's own words, what was executed and observed,
and a checklist of what the review expects; two of its boxes are true only of
someone who checked the list without reading it, or of an agent submitting
without human review, and checking either one closes the pull request.
CONTRIBUTING.md says where the code lives, what to run before opening a pull
request, that all six locales change together and that no AI attribution goes
into the history. AGENTS.md tells an assistant the same in its own terms, with
the traps that cost a review round: the web files the service embeds, the
locale and documentation directories that are named differently, the escaped
@ in a locale string, the Material colour and type tokens, and what in core/
belongs to v2rayA rather than to xray-core.
The page was 1400 px wide on the dashboard, proxies and subscriptions and
1040 px centred elsewhere, so the title and the header's buttons jumped
sideways on every change of view. The page is one width now and only the
body of a reading view is capped at 1040 px, left-aligned under the title.
The app bar's and the page header's group button go: the dashboard's group
card carries the picker with the member editing beside it, the header copy
had no such actions (from the chat).
NewUpdateStatus wrote the service's local time without a zone
("2006-1-2 15:04:05"); the browser read it as its own local time, so with the
service in UTC (a container, a router) and the browser in UTC+8 the dashboard
said "updated 8 hours ago" right after an update, as if the update had not
happened (#2046). The stamp is RFC 3339 now; dayjs reads the offset on both
pages, and stamps written before this keep reading as they did.
A submenu beside a phone-wide menu has nowhere to go and lands over its
parent. The batch bar's More actions and the node menu list the groups under
"Add to proxy group" and "Remove from proxy group" headings there; the
submenus stay from 600 dp.
- A page's late /touch response no longer writes the store after the page is
gone: useNodes marks itself disposed with its scope and apply() drops the
result, so leaving Subscriptions for Proxies while a request is in flight
cannot hand a batch action a stale member list.
- The dashboard's subscription card links go to the Subscriptions page, not
Proxies, which no longer lists subscriptions.
- Page shortcuts stay quiet while a menu is open (Escape dismissed the batch
menu and cleared the selection in one stroke) and treat checkboxes as
buttons, not text entry; the node checkboxes drop a keydown.stop that only
served the row activation that is gone.
- Submissions in flight are not started twice from the new Enter shortcuts:
GFWList update, subscription save, excluded domains, whitelist IPs.
- Choosing Documentation in the phone's app bar menu closes the menu.
- The Clash importer no longer writes allow_insecure into anytls and tuic
links (nothing reads it since 1c392550); the core's example configs drop the
stale key.
The proxies page grouped by a filter and by a click: a "Members only" chip
narrowed the list to the group in view, and clicking a card or a list row
joined the node to that group or took it out. Both are gone. Membership is
always asked for now: the node menu's Add to proxy group submenu lists every
group the core knows and marks the ones the node is already in, its Remove
from proxy group submenu lists the groups the node belongs to, and the batch
bar puts the same question for the whole selection. The in-use member picker
left with them - the dashboard's group card still picks the member the group
routes through - and the model state that only served it is gone.
Selection reaches both views: every node card carries a checkbox beside its
name, and the batch bar (select all, the count of selected nodes, test
latency, add to and remove from a group, delete, export) now sits above the
cards and not only above the list. Export asks where the sharing links go:
the clipboard as before, or a file named export- and the moment it was taken
(lib/download.ts). On a phone the bar keeps only test latency and folds the
rest into a More actions menu, whose export entries are flattened a level.
The dashboard's group card names the group it shows and switches it in place:
its header is the app bar's group button beside the words "Proxy group", and
its "Add nodes" button is "Add or remove nodes", which the title of the group
editor follows.
Six locales carry the new strings and drop the eighteen keys of the retired
group filter, the add-to-group dialog, the dashboard buttons and other
leftovers, and the six quick-start pages follow the renamed buttons.
v2rayA dropped allowInsecure years ago: VMess, VLESS and Trojan links carrying it
are parsed and the flag ignored, and a self-signed server is reached by pinning
its certificate. The three native protocols added in May brought the switch back
in their own config, service objects and forms. It goes everywhere: the core's
dialers verify or pin (the proto field 5 is reserved), the service no longer
parses, stores or exports allow_insecure for them, the forms lose the switch,
the codec ignores the parameter, and the quick-start docs say so in six locales.
Certificate pinning stays as it was.
The proxies page carried a second toolbar of group features: the group chips,
New group, the in-use member picker and the group settings/delete menu. The
app bar's group button already lists, creates, configures and deletes groups,
and the dashboard's group card already picks the member in use and edits the
members, so the row goes. Membership from the nodes page stays as node
actions: the card and its menu toggle the current group, and the batch bar's
Add to group / Remove from group open a menu of groups. The dashboard's
"Edit group" button is "Add nodes". Six quick-start pages follow.
useHotkeys: a window keydown listener for a page's life, silent while a dialog
is up or the user is typing (only Ctrl/Cmd+S reaches the page from a field).
Proxies: Ctrl/Cmd+A selects every listed node in the list view, Escape clears,
"/" goes to the search. Settings: Ctrl/Cmd+S saves what changed. Logs: "/"
goes to the search. Dialogs with a text area (import, subscription, excluded
domains, whitelist IPs, TUN processes, route scripts): Ctrl/Cmd+Enter submits;
the GFWList link field submits on Enter. The RoutingA editor already had
Ctrl+S and Tab. The quick-start docs list them in six locales.
The proxies page listed the subscriptions above the nodes behind a fold, and on
a phone its toolbar, the fold, the node toolbar and the group row stacked into
a wall of buttons. Subscriptions are a destination of their own now: the cards,
Auto-update and Import a subscription, sharing the proxies model. The bottom
bar keeps Material's five (dashboard, proxies, subscriptions, settings, logs);
on a phone the docs are a button in the app bar next to the groups and the
menu, and under 440 px the bar shows the logo without the wordmark so the
status pill and the three buttons fit (measured at 320 to 430; the wordmark is
back from 440, where it has room). The rail and the drawer list all six. The
quick-start docs say so in six locales.
The Release_to_AUR job of _release.yml moves to _release_aur.yml (workflow_call,
input tag); the release calls it as before, after GitHub_Release and only with
publish_downstream. release_aur.yml runs it alone from workflow_dispatch, for the
case where the release went through and only the AUR step failed, as with 2.5.5.
833af7dc replaced 'git add .SRCINFO .INSTALL && git commit -a' with 'git add -A',
which also staged the installer_archlinux_*.pkg.tar.zst that updpkgsums downloads
into aur/v2raya-bin; the AUR hook rejected the 2.5.5 push (maximum blob size
488.28KiB exceeded). 'git add -u' stages the PKGBUILD and .SRCINFO changes and
the .INSTALL deletion, and nothing new.