Auto-sync: 2026-04-16 20:05
This commit is contained in:
31
wiki/concepts/Clash.md
Normal file
31
wiki/concepts/Clash.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: Clash
|
||||
type: concept
|
||||
tags: [proxy, 科学上网]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Summary
|
||||
- 定义:基于Go语言开发的代理客户端,支持规则分流
|
||||
- 内核:GitHub开源项目 clash/clash
|
||||
- 特点:高性能、支持多种协议、支持规则分流
|
||||
|
||||
## Key Characteristics
|
||||
- 支持代理协议:Shadowsocks、ShadowsocksR、V2Ray、Trojan、HTTP、SOCKS5
|
||||
- 支持规则分流:根据域名、IP、地理位置等分流
|
||||
- 支持策略组:自动测速、自动选择最优节点
|
||||
- 支持GeoIP规则:国内直连、海外代理
|
||||
|
||||
## Components
|
||||
- 配置文件(YAML格式):定义规则和节点
|
||||
- 订阅链接:远程配置文件URL
|
||||
- Dashboard:Web管理界面
|
||||
|
||||
## Use Cases
|
||||
- 路由器梅林固件上的科学上网(MerlinClash)
|
||||
- PC/Mac端科学上网
|
||||
- 安卓/iOS端科学上网
|
||||
|
||||
## Connections
|
||||
- [[Clash]] ← implements ← [[科学上网]]
|
||||
- [[MerlinClash]] ← based_on ← [[Clash]]
|
||||
49
wiki/concepts/Cloud-Operating-Model.md
Normal file
49
wiki/concepts/Cloud-Operating-Model.md
Normal file
@@ -0,0 +1,49 @@
|
||||
---
|
||||
title: "Cloud Operating Model"
|
||||
type: concept
|
||||
tags: [cloud, governance, operating-model]
|
||||
sources: [Cloud-Operating-Model-Key-Strategies-and-Best-Practices]
|
||||
last_updated: 2026-04-16
|
||||
---
|
||||
|
||||
## Summary
|
||||
Cloud Operating Model(云运营模型)是组织管理云资源、安全、成本和治理的框架,是现代云战略的支柱。
|
||||
|
||||
## Definition
|
||||
云运营模型定义了组织如何在云环境中运营,确保治理、安全、成本优化和运营敏捷性的平衡。
|
||||
|
||||
## Four Pillars
|
||||
1. **Governance & Compliance**(治理与合规):标准化治理确保跨云环境合规
|
||||
2. **Automation**(自动化):IaC、CI/CD、事件驱动自动化提升效率
|
||||
3. **Security**(安全):Zero Trust、加密、实时监控
|
||||
4. **Cost Management(FinOps)**:成本追踪、优化和预算控制
|
||||
|
||||
## Implementation Steps
|
||||
1. **评估云成熟度**:确定组织当前所处阶段(Ad-hoc → Cloud-Native)
|
||||
2. **建立治理框架**:定义 IAM 角色、策略、审计规则
|
||||
3. **自动化运营**:采用 IaC、CI/CD、Serverless
|
||||
4. **实施 FinOps**:实时成本监控、预留实例、自动扩缩容
|
||||
5. **强化安全**:Zero Trust、自动合规检查、威胁检测
|
||||
6. **持续优化**:AIOps、自我修复系统、AI 驱动决策
|
||||
|
||||
## Key Benefits
|
||||
- 标准化治理 → 确保跨环境合规
|
||||
- 成本优化 → 防止超支
|
||||
- 改进安全 → 自动化策略和访问控制
|
||||
- 运营敏捷 → DevOps、CI/CD、自动扩缩容
|
||||
- 多云灵活性 → 减少供应商锁定
|
||||
|
||||
## Industry Applications
|
||||
- **金融**:自动化合规、成本治理、Zero Trust
|
||||
- **医疗**:自动合规执行、数据加密、AI 诊断
|
||||
- **零售**:自动扩缩容、多云策略
|
||||
- **SaaS**:DevOps 加速、容器化架构、DevSecOps
|
||||
|
||||
## Connections
|
||||
- [[Cloud Operating Model]] ← extends ← [[Cloud Maturity Model]]
|
||||
- [[Cloud Operating Model]] ← includes ← [[Governance Framework]]
|
||||
- [[Cloud Operating Model]] ← includes ← [[FinOps]]
|
||||
- [[Cloud Operating Model]] ← includes ← [[Zero Trust Architecture]]
|
||||
- [[Cloud Operating Model]] ← includes ← [[AIOps]]
|
||||
- [[Multi-Cloud Strategy]] ← enabled_by ← [[Cloud Operating Model]]
|
||||
- [[Cloud Adoption]] ← requires ← [[Cloud Operating Model]]
|
||||
44
wiki/concepts/Docker-Compose.md
Normal file
44
wiki/concepts/Docker-Compose.md
Normal file
@@ -0,0 +1,44 @@
|
||||
---
|
||||
title: "Docker-Compose"
|
||||
type: concept
|
||||
tags: [docker, container, orchestration]
|
||||
---
|
||||
|
||||
## Definition
|
||||
Docker Compose(Docker Compose V2)是 Docker 官方提供的多容器 Docker 应用定义和运行工具,通过 `docker-compose.yml` 文件声明式配置多容器应用。
|
||||
|
||||
## Core Components
|
||||
- **Services**:定义每个容器配置
|
||||
- **Volumes**:持久化数据卷
|
||||
- **Networks**:容器网络配置
|
||||
- **Profiles**:条件性启动服务
|
||||
|
||||
## Key Features
|
||||
- 单一命令启动整个应用:`docker compose up`
|
||||
- 服务依赖管理
|
||||
- 环境变量配置
|
||||
- 端口映射
|
||||
- 卷挂载
|
||||
|
||||
## Syntax Example
|
||||
```yaml
|
||||
services:
|
||||
web:
|
||||
image: nginx
|
||||
ports:
|
||||
- "80:80"
|
||||
volumes:
|
||||
- ./html:/usr/share/nginx/html
|
||||
```
|
||||
|
||||
## Use Cases
|
||||
- 本地开发环境搭建
|
||||
- 微服务应用部署
|
||||
- CI/CD 测试环境
|
||||
- Home Lab 应用(如 Navidrome、Pi-hole 等)
|
||||
|
||||
---
|
||||
|
||||
## Related
|
||||
- [[Navidrome]] — 使用 Docker-Compose 部署的服务
|
||||
- [[Docker]] — 容器运行时
|
||||
32
wiki/concepts/FinOps.md
Normal file
32
wiki/concepts/FinOps.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "FinOps"
|
||||
type: concept
|
||||
tags: [cloud, finops, cost-management, financial-operations]
|
||||
sources: [Cloud-Operating-Model-Key-Strategies-and-Best-Practices]
|
||||
last_updated: 2026-04-16
|
||||
---
|
||||
|
||||
## Summary
|
||||
FinOps(云财务运营)是整合财务管理与云资源优化的实践,旨在实现云支出的可见性、控制和持续优化。
|
||||
|
||||
## Definition
|
||||
FinOps 弥合了传统财务与云工程团队之间的差距,通过实时监控、智能分析和自动化优化确保云支出合理。
|
||||
|
||||
## Key Practices
|
||||
- **成本可见性**:跨云、跨团队的成本分配和追踪
|
||||
- **实时监控**:使用 AWS Cost Explorer、Azure Cost Management、GCP Billing Reports
|
||||
- **自动化优化**:预留实例、Spot 实例、自动扩缩容
|
||||
- **预算告警**:设置阈值,超过时自动通知
|
||||
- **持续优化**:定期审查资源使用情况,淘汰闲置资源
|
||||
|
||||
## Metrics
|
||||
- **Cloud Cost Efficiency**:云成本效率 = 业务价值 / 云支出
|
||||
- **Unit Cost**:单位成本 = 总支出 / 产出单位
|
||||
- **Savings Rate**:储蓄率 =(优化前支出 - 优化后支出)/ 优化前支出
|
||||
|
||||
## Connections
|
||||
- [[Cloud Operating Model]] ← includes ← [[FinOps]]
|
||||
- [[Cost Optimization]] ← implements ← [[FinOps]]:成本优化是 FinOps 的核心
|
||||
- [[Pay-as-you-go]] ← enabled_by ← [[FinOps]]:FinOps 优化按需付费模式
|
||||
- [[AIOps]] ← optimizes ← [[FinOps]]:AI 驱动的 FinOps 可预测成本趋势
|
||||
- [[Multi-Cloud]] ← requires ← [[FinOps]]:多云环境尤其需要 FinOps
|
||||
46
wiki/concepts/NFS永久挂载.md
Normal file
46
wiki/concepts/NFS永久挂载.md
Normal file
@@ -0,0 +1,46 @@
|
||||
---
|
||||
title: "NFS永久挂载"
|
||||
type: concept
|
||||
tags: [mount, nfs, fstab]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
NFS 永久挂载是指通过配置文件实现网络文件系统(NFS)在系统开机时自动挂载,而不是依赖手动执行 mount 命令。Linux 系统通过 /etc/fstab 文件管理所有文件系统挂载点。
|
||||
|
||||
## Implementation
|
||||
在 /etc/fstab 中添加配置行:
|
||||
```
|
||||
192.168.3.17:/volume2/backup /mnt/nas_backup nfs defaults,timeo=900,retrans=5,_netdev 0 0
|
||||
```
|
||||
|
||||
## Key Parameters
|
||||
- **defaults**:使用默认挂载参数(rw, suid, dev, exec, auto, nouser, async)
|
||||
- **timeo=900**:超时时间 90 秒(单位 1/10 秒)
|
||||
- **retrans=5**:超时重试次数 5 次
|
||||
- **_netdev**:关键参数,指定为网络设备,等待网络服务启动后再挂载
|
||||
|
||||
## Why _netdev is Critical
|
||||
_netdev 参数告诉系统:
|
||||
1. 这是一个网络文件系统
|
||||
2. 必须等到网络服务完全启动后再尝试挂载
|
||||
3. 防止开机过程因网络未就绪而卡死
|
||||
|
||||
## Testing
|
||||
```bash
|
||||
# 卸载当前挂载
|
||||
sudo umount /mnt/nas_backup
|
||||
# 模拟开机挂载
|
||||
sudo mount -a
|
||||
# 验证挂载
|
||||
df -h | grep nas_backup
|
||||
```
|
||||
|
||||
## Common Issues
|
||||
- **挂载失效**:nfs-common 服务启动慢于 mount -a 执行
|
||||
- **解决**:启用 remote-fs.target 服务:`sudo systemctl enable remote-fs.target`
|
||||
|
||||
## Related Entities
|
||||
- [[NFS]]:网络文件系统协议
|
||||
- [[NAS]]:网络附加存储设备
|
||||
|
||||
21
wiki/concepts/Shell.md
Normal file
21
wiki/concepts/Shell.md
Normal file
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: "Shell"
|
||||
type: concept
|
||||
tags: [linux, shell]
|
||||
sources: ["raw/Home Office/Linux 运维必会的 150 个命令.md"]
|
||||
last_updated: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
Shell(命令解释器)是 Linux 系统的用户界面,负责解释和执行用户输入的命令。它作为用户与内核之间的桥梁,将用户的命令转换为系统调用。
|
||||
|
||||
## Common Types
|
||||
- **Bash**:最常用的 Shell,Linux 默认
|
||||
- **Zsh**:功能强大的增强版 Shell
|
||||
- **Fish**:用户友好的交互式 Shell
|
||||
|
||||
## Related Commands
|
||||
- help:查看内置命令帮助
|
||||
- type:判断命令是否为内置命令
|
||||
- alias:设置命令别名
|
||||
- unalias:取消命令别名
|
||||
61
wiki/concepts/systemd.md
Normal file
61
wiki/concepts/systemd.md
Normal file
@@ -0,0 +1,61 @@
|
||||
---
|
||||
id: systemd
|
||||
title: "systemd"
|
||||
type: concept
|
||||
tags: [linux, service-manager]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
systemd 是 Linux 系统的服务管理器,负责管理系统进程、服务和启动项,是大多数现代 Linux 发行版的初始系统。
|
||||
|
||||
## Key Components
|
||||
- **systemd**:系统和服务管理器
|
||||
- **systemctl**:命令行管理工具
|
||||
- **journald**:日志收集系统
|
||||
- **unit files**:服务配置文件(.service)
|
||||
|
||||
## Common Commands
|
||||
```bash
|
||||
# 启动服务
|
||||
sudo systemctl start <service>
|
||||
|
||||
# 停止服务
|
||||
sudo systemctl stop <service>
|
||||
|
||||
# 重启服务
|
||||
sudo systemctl restart <service>
|
||||
|
||||
# 查看状态
|
||||
sudo systemctl status <service>
|
||||
|
||||
# 开机自启
|
||||
sudo systemctl enable <service>
|
||||
|
||||
# 禁用开机自启
|
||||
sudo systemctl disable <service>
|
||||
|
||||
# 查看日志
|
||||
sudo journalctl -u <service>
|
||||
```
|
||||
|
||||
## Unit File Structure
|
||||
```ini
|
||||
[Unit]
|
||||
Description=<description>
|
||||
After=network-online.target
|
||||
Wants=network-online.target
|
||||
|
||||
[Service]
|
||||
Type=simple
|
||||
ExecStart=/path/to/executable
|
||||
Restart=on-failure
|
||||
RestartSec=10
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
```
|
||||
|
||||
## Connections
|
||||
- [[systemd]] ← manages ← [[Linux系统服务]]
|
||||
- [[systemd]] ← writes_logs_to ← [[journald]]
|
||||
32
wiki/concepts/内网穿透.md
Normal file
32
wiki/concepts/内网穿透.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
id: nei-wang-chuan-tou
|
||||
title: "内网穿透"
|
||||
type: concept
|
||||
tags: [networking, nat, proxy]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
内网穿透(NAT Penetration)是一种将内网服务通过公网服务器暴露给外部访问的技术,又称端口映射或反向代理。
|
||||
|
||||
## Key Mechanisms
|
||||
- **端口映射**:将内网端口映射到公网端口
|
||||
- **反向代理**:公网服务器接收请求后转发到内网
|
||||
- **心跳保活**:维持 NAT 映射有效性的机制
|
||||
- **UDP 打洞**:通过 UDP 穿透 NAT 的技术
|
||||
|
||||
## Tools
|
||||
- [[FRP]]:Fast Reverse Proxy,开源内网穿透工具
|
||||
- [[NAT穿透]]:内网穿透的另一种称呼
|
||||
- ngrok:商业内网穿透服务
|
||||
- frp:开源方案
|
||||
|
||||
## Use Cases
|
||||
- 远程访问内网 SSH
|
||||
- 暴露本地 Web 服务到公网
|
||||
- 远程调试和开发
|
||||
- IoT 设备远程管理
|
||||
|
||||
## Connections
|
||||
- [[内网穿透]] ← implemented_by ← [[FRP]]
|
||||
- [[内网穿透]] ← uses ← [[NAT穿透]]
|
||||
35
wiki/concepts/增量备份.md
Normal file
35
wiki/concepts/增量备份.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: "增量备份"
|
||||
type: concept
|
||||
tags: [backup, strategy]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
增量备份(Incremental Backup)是一种数据备份策略,仅备份自上次备份以来发生变化的文件和数据。与全量备份相比,它显著减少了备份时间和存储空间占用。
|
||||
|
||||
## How It Works
|
||||
1. 首次备份:执行全量备份(Full Backup)
|
||||
2. 后续备份:仅备份相较于上次备份发生变化的数据
|
||||
3. 恢复时:需要依次恢复全量备份 + 所有增量备份
|
||||
|
||||
## Advantages
|
||||
- **节省存储空间**:仅存储变化数据
|
||||
- **备份速度快**:无需扫描和传输全部数据
|
||||
- **减少网络负载**:尤其适合远程备份场景
|
||||
- **支持不关机运行**:可在业务运行时执行
|
||||
|
||||
## Common Tools
|
||||
- [[rsync]]:Linux/Unix 环境下最常用的增量同步工具
|
||||
- rdiff-backup:支持增量备份和远程备份
|
||||
- Borg: deduplicating 备份程序
|
||||
|
||||
## Related Concepts
|
||||
- [[全量备份]]:完整的系统/数据快照
|
||||
- [[差异备份]]:仅备份相较于初始全量备份的变化
|
||||
- [[RPO]]:恢复点目标,决定备份频率
|
||||
|
||||
## Related Entities
|
||||
- [[rsync]]:实现增量备份的核心工具
|
||||
- [[NAS]]:增量备份的常用目标存储
|
||||
|
||||
35
wiki/concepts/故障转移.md
Normal file
35
wiki/concepts/故障转移.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: 故障转移
|
||||
type: concept
|
||||
tags: [failover, network]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Failover
|
||||
- 自动故障转移
|
||||
|
||||
## Summary
|
||||
- 定义:当主节点不可用时自动切换到备用节点的机制
|
||||
- 目的:保证网络连接的持续性
|
||||
- 应用:科学上网、负载均衡等场景
|
||||
|
||||
## Key Characteristics
|
||||
- 定期检测节点延迟
|
||||
- 主节点故障时自动切换
|
||||
- 切换后可能自动恢复主节点
|
||||
- 支持多个备用节点
|
||||
|
||||
## In 科学上网 Context
|
||||
- 自动延迟测试(每若干分钟)
|
||||
- 节点不可达时自动切换
|
||||
- 支持策略组配置多个节点
|
||||
|
||||
## Related Concepts
|
||||
- [[科学上网]]:故障转移的主要应用场景
|
||||
- [[Clash]]:支持故障转移的代理工具
|
||||
- [[High-Availability]]:更广泛的可用性概念
|
||||
|
||||
## Connections
|
||||
- [[故障转移]] ← enables ← [[科学上网]]
|
||||
- [[Clash]] ← supports ← [[故障转移]]
|
||||
35
wiki/concepts/梅林固件.md
Normal file
35
wiki/concepts/梅林固件.md
Normal file
@@ -0,0 +1,35 @@
|
||||
---
|
||||
title: 梅林固件
|
||||
type: concept
|
||||
tags: [router, firmware]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- Merlin Firmware
|
||||
- 华硕梅林固件
|
||||
|
||||
## Summary
|
||||
- 定义:华硕路由器官方固件的第三方增强版,由asuswrt修改而来
|
||||
- 特点:功能丰富、稳定性高、支持更多插件和高级网络配置
|
||||
- 适用设备:华硕、网件部分型号路由器
|
||||
|
||||
## Key Characteristics
|
||||
- 基于华硕asuswrt源代码
|
||||
- 支持软件中心(Software Center)安装插件
|
||||
- 支持更多自定义配置
|
||||
- 定期更新维护
|
||||
- 支持科学上网插件
|
||||
|
||||
## Use Cases
|
||||
- 刷入梅林固件以安装科学上网插件
|
||||
- 扩展路由器功能(如广告屏蔽、流量监控)
|
||||
- 实现更精细的QoS配置
|
||||
|
||||
## Related Concepts
|
||||
- [[故障转移]]:梅林固件插件支持自动故障转移
|
||||
- [[Clash]]:运行在梅林固件上的代理工具
|
||||
|
||||
## Connections
|
||||
- [[Netgear]] ← supports_firmware ← [[梅林固件]]
|
||||
- [[MerlinClash]] ← runs_on ← [[梅林固件]]
|
||||
52
wiki/concepts/灾难恢复.md
Normal file
52
wiki/concepts/灾难恢复.md
Normal file
@@ -0,0 +1,52 @@
|
||||
---
|
||||
title: "灾难恢复"
|
||||
type: concept
|
||||
tags: [recovery, backup, dr]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Definition
|
||||
灾难恢复(Disaster Recovery,DR)是指在系统发生严重故障(如硬盘损坏、系统崩溃、自然灾害)后,恢复业务运营和数据完整性的过程。灾难恢复计划(DRP)是企业 IT 运维的关键组成部分。
|
||||
|
||||
## Key Metrics
|
||||
- **RTO(恢复时间目标)**:系统允许的最大停机时间
|
||||
- **RPO(恢复点目标)**:可接受的最大数据丢失量
|
||||
|
||||
## Recovery Strategies
|
||||
|
||||
### Level 1: 文件级恢复
|
||||
- 场景:单个文件丢失或误删除
|
||||
- 方法:从备份目录直接拷贝恢复
|
||||
- 工具:cp、rsync
|
||||
|
||||
### Level 2: 系统级恢复
|
||||
- 场景:系统崩溃但能通过 SSH 访问
|
||||
- 方法:反向执行 rsync,从备份恢复
|
||||
- 命令:`sudo rsync -aAXz /mnt/nas_backup/daily_sync/ /`
|
||||
|
||||
### Level 3: 整机恢复
|
||||
- 场景:硬盘完全损坏
|
||||
- 方法:
|
||||
1. 使用 [[Clonezilla]] 恢复系统镜像
|
||||
2. 使用 [[rsync]] 同步最新的增量数据
|
||||
3. 实现"时间点恢复"
|
||||
|
||||
## Best Practices
|
||||
1. **3-2-1 备份原则**:3 份副本、2 种介质、1 份异地
|
||||
2. **定期测试恢复流程**:确保备份可用
|
||||
3. **自动化备份**:使用 [[定时任务]] 实现无人值守
|
||||
4. **分层备份**:
|
||||
- 实时:rsync 增量备份
|
||||
- 每日:全量备份
|
||||
- 周期性:Clonezilla 镜像
|
||||
|
||||
## Related Concepts
|
||||
- [[增量备份]]:日常数据保护手段
|
||||
- [[RTO]]:恢复时间目标
|
||||
- [[RPO]]:恢复点目标
|
||||
|
||||
## Related Entities
|
||||
- [[Clonezilla]]:整机镜像备份工具
|
||||
- [[rsync]]:增量同步工具
|
||||
- [[NAS]]:备份存储目标
|
||||
|
||||
43
wiki/concepts/科学上网.md
Normal file
43
wiki/concepts/科学上网.md
Normal file
@@ -0,0 +1,43 @@
|
||||
---
|
||||
title: 科学上网
|
||||
type: concept
|
||||
tags: [科学上网, proxy]
|
||||
date: 2026-04-16
|
||||
---
|
||||
|
||||
## Aliases
|
||||
- 翻墙
|
||||
- 科学上网工具
|
||||
- 科学冲浪
|
||||
|
||||
## Summary
|
||||
- 定义:通过代理服务器绕过网络限制访问被封锁网站的技术
|
||||
- 原理:用户客户端 → 代理服务器(境外)→ 目标网站
|
||||
- 协议:Shadowsocks、ShadowsocksR、V2Ray、Trojan等
|
||||
|
||||
## Key Characteristics
|
||||
- 通过订阅链接导入节点配置
|
||||
- 支持自动/手动节点选择
|
||||
- 支持规则分流(国内外流量分离)
|
||||
- 支持自动故障转移
|
||||
|
||||
## Components
|
||||
- 机场:提供代理服务器的服务商
|
||||
- 订阅链接:节点配置的URL地址
|
||||
- 客户端:运行代理协议的软件
|
||||
|
||||
## Use Cases
|
||||
- 访问Google、YouTube、Twitter等被限制网站
|
||||
- 解锁Netflix等流媒体地区限制
|
||||
- 保护网络隐私和安全
|
||||
|
||||
## Related Concepts
|
||||
- [[Clash]]:一种支持规则分流的代理客户端
|
||||
- [[SSR]]:ShadowsocksR协议
|
||||
- [[V2Ray]]:另一种代理协议
|
||||
- [[Trojan]]:基于TLS的代理协议
|
||||
|
||||
## Connections
|
||||
- [[科学上网]] ← implements ← [[Clash]]
|
||||
- [[科学上网]] ← implements ← [[SSR]]
|
||||
- [[故障转移]] ← enables ← [[科学上网]]
|
||||
Reference in New Issue
Block a user