Files
v2rayA/core
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
..
2026-05-02 11:58:21 +08:00