Skip to content

run.md

Latest commit

 

History

History
40 lines (29 loc) · 1.33 KB

run.md

File metadata and controls

40 lines (29 loc) · 1.33 KB

Run

Runtime Requirements

  • Windows 10 or later, 64-bit.
  • WinpkFilter / ndisapi runtime DLL next to WinTProxy.exe:
    • ndisapi.dll
  • WinpkFilter driver installed. Use the release installer so driver signing and service setup are handled for you.
  • A SOCKS5 proxy reachable by IPv4 address.

Usage

WinTProxy.exe --config config.example.json
WinTProxy.exe --config config.example.json -vv
WinTProxy.exe --config config.example.json --log wintproxy.log
WinTProxy.exe [options]

Options:
  --config <path>     Path to JSON config file
  --log <path>        Override logging.file from config
  -v, --verbose       Override logging.level (-v=info, -vv=debug, -vvv=trace; -vvvv also clamps to trace)
  --version           Show version
  -h, --help          Show help

Traffic behavior lives in JSON. CLI flags only cover bootstrap, logging, help, and version. The former traffic override flags were removed so runtime behavior has one source of truth.

Startup Order

WinTProxy initializes stateful subsystems before interception starts:

Winsock -> Config -> Conntrack -> Process lookup -> DNS hijack -> TCP relay -> UDP relay -> ndisapi engine

Shutdown reverses ownership-sensitive services so relay traffic is closed before packet interception is stopped.