|
33 | 33 | 2. **balanced** — long-lived reused circuits (fewer handshakes) |
34 | 34 | 3. **aggressive** — more guards + faster scheduler + deeper reuse |
35 | 35 | 4. **ultimate** — max concurrency + greedy (Vanilla) scheduler |
36 | | - 5. **lowlatency** — lowest ping: KISTLite pacing and RTT set filters |
37 | | - (skip ≥400 ms, best 20%) — **the shipped default strategy** |
| 36 | + 5. **lowlatency** — lowest ping: KISTLite pacing and RTT set filters |
| 37 | + (skip ≥400 ms, best 20%) |
| 38 | + - The **shipped default strategy** is **ultimate** — if no |
| 39 | + `data\strategy.txt` exists yet, TorJet picks the fastest preset. |
38 | 40 | - **Conflux topology** (from the Settings submenu) — how many conflux |
39 | 41 | circuit sets tor keeps: |
40 | 42 | - **Conflux sets** (`ConfluxNumSets`, 0=consensus default) — how many |
@@ -141,6 +143,21 @@ circuit guard -> middle -> exit |
141 | 143 | destination |
142 | 144 | ``` |
143 | 145 |
|
| 146 | +### Tunneling apps that don't support proxy |
| 147 | + |
| 148 | +Some applications (games, CLI tools, etc.) don't have built-in proxy settings. |
| 149 | +You can route their traffic through Tor using **V2rayN** as a TUN wrapper: |
| 150 | + |
| 151 | +1. Start TorJet and wait for 100% bootstrap. |
| 152 | +2. Open V2rayN and add a new server with this address: |
| 153 | + ``` |
| 154 | + socks://Og@127.0.0.1:9050#TorJet |
| 155 | + ``` |
| 156 | +3. Select the TorJet server and enable **Tun** mode. |
| 157 | + |
| 158 | +V2rayN will create a virtual network interface that captures all system |
| 159 | +traffic and sends it through TorJet's SOCKS5 proxy (127.0.0.1:9050). |
| 160 | + |
144 | 161 | ### Circuit health monitor |
145 | 162 |
|
146 | 163 | While Tor is up, TorJet watches the conflux legs via the control port. Every |
@@ -194,7 +211,7 @@ would normally skip them. The loop runs |
194 | 211 | in the background while the menu is served (so the menu appears immediately) and |
195 | 212 | stops only when you press **C**, tor exits, or the app is closed. It keeps |
196 | 213 | circuits warm and honest: if tor dies, the pings start failing (details go to |
197 | | -`data\data\jet.log`). The old 1 MiB download check was replaced: it gave false |
| 214 | +`data\jet.log`). The old 1 MiB download check was replaced: it gave false |
198 | 215 | negatives on cold single-stream circuits and added ~1 MiB of padding traffic. |
199 | 216 | During the first 90 s after bootstrap the monitor's close cooldown is relaxed, |
200 | 217 | so weak legs are replaced immediately. |
|
0 commit comments