okooooooo/3m-ui
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: remove Cloudflare WARP feature (panel, API, docs)

Browse Source 
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
chore: remove Cloudflare WARP feature (panel, API, docs)
Drop register/inject endpoints, Settings/Routing UI, server-exit WARP
path, and documentation. Client routing and inbound panel unchanged;
server remains MATCH,DIRECT.
This commit is contained in:
kazeyukiro committed 2026-09-23 17:05:13 +00:00
1 parent ca548e29c9
commit 52bb97c083
39 files changed
+25 -1743
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/routing.md
+7 -101
View File
@@ -1,105 +1,11 @@
<!-- server split removed: visual routing is client-subscription only -->
# Routing & proxy-groups
# Routing (client subscription)
Panel page **Routing** edits the **client subscription** layout only (`proxy-groups` + `rules` in `visual-config`). Mihomo/Clash YAML subscriptions export these groups with your nodes injected into leaf selects.
The **Routing** page edits **client subscription** layout only: Mihomo/Clash `proxy-groups` and `rules` stored in the `visual-config` fragment.
**Server-side split is disabled:** the panel Mihomo process always uses `MATCH,DIRECT` (inbound panel). Visual rules/groups/proxies are **not** merged into the serving `config.yaml`.
- Community templates (YiXuanZX / echs-top / AIsouler) fill groups + rules for the **client** YAML.
- After **Save**, update the subscription in the client (Mihomo/Clash YAML target).
- The **panel Mihomo process** always uses `MATCH,DIRECT` (inbound panel). Visual rules/groups/proxies are **not** merged into the serving `config.yaml`.
## Defaults
## Config engine
Fresh install uses:
```text
MATCH,DIRECT
```
That is intentional for a **server inbound** panel: client traffic that reaches this host leaves via DIRECT unless you add rules.
## Structured rules (UI)
Each rule has:
| Field | Meaning |
|-------|---------|
| Type | e.g. `DOMAIN`, `DOMAIN-SUFFIX`, `GEOIP`, `GEOSITE`, `IP-CIDR`, `MATCH`, … |
| Payload | Match value (empty for `MATCH`) |
| Target | `DIRECT`, `REJECT`, a **proxy-group** name, or an outbound **proxy** name |
| no-resolve | Optional on `IP-CIDR` / `IP-CIDR6` / `GEOIP` |
Rules can be reordered. Advanced lines that the UI cannot parse are kept as **raw** and saved unchanged.
**Save** writes the database. Rules take effect only after **Generate & apply** (same path as node config).
### Validation
- Type, target required; payload required except `MATCH`
- Warning if the last rule is not `MATCH`
### Templates
| Template | Result |
|----------|--------|
| DIRECT only | `MATCH,DIRECT` |
| CN direct | `GEOIP,CN,DIRECT` + `MATCH,<first group or PROXY>` |
| Sample ads | Several `DOMAIN-*` → `REJECT` + `MATCH,DIRECT` |
| Via group | `MATCH,<first group or PROXY>` |
### WARP inject
**Routing → WARP** calls `POST /api/v1/config/routing/inject-warp`:
1. Registers Cloudflare WARP
2. Merges the outbound into `visual-config` proxies
3. Optional rule update: none / final `MATCH,<name>` / `GEOIP,CN,DIRECT` + `MATCH,<name>`
Then generate & apply. Requires the panel host to reach Cloudflare.
## Proxy-groups
Simple groups: `select` / `url-test` / `fallback` / `load-balance`, member list, optional URL/interval for url-test.
## APIs
```http
GET/PUT /api/v1/config/rules
GET/PUT /api/v1/config/groups
POST /api/v1/config/routing/inject-warp
```
```json
{ "mode": "wireguard", "rule_mode": "match", "name": "WARP-OUT" }
```
`rule_mode`: `none` | `match` | `cn_direct`.
Also related: `GET/POST /api/v1/config/proxies`, visual config under **Config**.
## Related
- [Installation](installation.md) — frontend stack
- [Cluster](cluster.md) — multi-panel (separate from Mihomo rules)
## Community rule templates
Routing → **Templates** includes adaptations of public Mihomo rule projects (for server visual-config; not a full client overwrite script):
| Template | Upstream | Intent |
|----------|----------|--------|
| YiXuanZX/rules | [YiXuanZX/rules](https://github.com/YiXuanZX/rules) | Groups: 香港/新加坡/日本/美国/其他 + **代理 / AI / TG**. Rules: CN direct, OpenAI→AI, Telegram→TG, GFW→代理 |
| echs-top/proxy | [echs-top/proxy](https://github.com/echs-top/proxy) | Groups: **代理连接 / TELEGRAM / 国外AI / GOOGLE / 海外媒体 / …**. Ads REJECT + CN direct + category rules |
| AIsouler/MyClash | [AIsouler/MyClash](https://github.com/AIsouler/MyClash) | Groups: **直连 / AdBlock / Google / AI / Telegram / Steam / 默认代理 / 漏网之鱼**. Lite GEOSITE map |
Applying a community template **writes matching proxy-groups** (merged by name) and rules. Leaf members use existing visual outbounds if any, else `DIRECT` — put real nodes/WARP into the region or policy groups afterward.
These use **GEOSITE/GEOIP** against MetaCubeX geodata (Settings → Geo). Full upstream `rule-providers` / region filters remain optional via custom YAML fragments.
## Server WARP exit (user → node → WARP IP)
1. Routing page → **Inject WARP** (optional rule: all MATCH WARP, or CN DIRECT + MATCH WARP).
2. **Save** then **Generate & apply**.
3. Panel Mihomo loads the WireGuard outbound and sets `MATCH,<WARP name>` (community templates stay client-only).
4. User traffic through listeners exits with a Cloudflare WARP IP.
Remove WARP proxies from visual-config (or clear routing proxies) and re-apply to return to `MATCH,DIRECT`.
**Generate & apply** rebuilds listener config for the server core. It does not apply client community rules to the host process.