路由配置网 / 配置搜索
搜索网络配置知识库
显示全部 242 篇文章
DNS HubDHCPNASOpenWrtNetwork Problem GraphRouting HubDHCPIPv4Network Problem GraphDNS HubNAT64DNS64IPv6Network Problem GraphRouting HubIPv6RouterOpenWrtNetwork Problem GraphRouting HubNATDNSOpenWrtNetwork Problem GraphDNS HubOpenWrtdnsmasqRouting HubNetwork Problem GraphError HubIPv6RouterFirewallNetwork Problem GraphiOSDNStvOSDNS全局模式回滚iPadOSProfileiOSStash规则CIDRDNSfake-ip日志调试策略组健康检查MihomoYAML规则集版本TUN路由表MTU延迟SOP可观测性OpenWrt网关DNSAdGuard策略路由DHCP透明转发防火墙DNS HubAdGuard HomeNetwork Problem GraphDNS HubAI NetworkNetwork Problem GraphProtocol HubAI NetworkNetwork Problem GraphError HubAI NetworkNetwork Problem GraphDevice HubAI NetworkNetwork Problem GraphDevice HubAI NetworkNetwork Problem GraphDevice HubPhoneNetwork Problem GraphDevice HubAndroid TVNetwork Problem GraphDevice HubVLANNetwork Problem GraphDevice HubApple TVNetwork Problem GraphDevice HubApple TVNetwork Problem GraphDevice HubApple TVNetwork Problem GraphDevice HubApple TVNetwork Problem GraphDevice HubApple TVNetwork Problem GraphDevice HubApple TVNetwork Problem GraphError HubARPNetwork Problem GraphError HubEthernetNetwork Problem GraphRouting HubMulticastNetwork Problem GraphRouting HubEthernetNetwork Problem GraphRouting HubVLANNetwork Problem GraphRouting HubBufferbloatNetwork Problem GraphRouting HubCAKENetwork Problem GraphRouting HubCAKENetwork Problem GraphRouting HubCGNATNetwork Problem GraphRouting HubRoutingNetwork Problem GraphError HubDHCPNetwork Problem GraphRouting HubDHCPNetwork Problem GraphDNS HubDHCPNetwork Problem GraphRouting HubDHCPNetwork Problem GraphRouting HubDHCPNetwork Problem GraphRouting HubDHCPv6Network Problem GraphDNS HubDNSNetwork Problem GraphDNS HubDNSNetwork Problem GraphDNS HubDNSNetwork Problem GraphDevice HubDNS-SDNetwork Problem GraphDNS HubDNSNetwork Problem GraphDNS HubDNSNetwork Problem GraphDNS HubDNSSECNetwork Problem GraphDNS HubDNSSECNetwork Problem GraphDNS HubDNSSECNetwork Problem GraphDevice HubDockerNetwork Problem GraphError HubDockerNetwork Problem GraphDevice HubDockerNetwork Problem GraphDevice HubDockerNetwork Problem GraphDNS HubDoHNetwork Problem GraphDNS HubDoTNetwork Problem GraphRouting HubQoSNetwork Problem GraphRouting HubGatewayNetwork Problem GraphError HubARPNetwork Problem GraphDNS HubEDNSNetwork Problem GraphDevice HubEthernetNetwork Problem GraphDevice HubEthernetNetwork Problem GraphRouting HubFirewallNetwork Problem GraphDevice HubNASNetwork Problem GraphRouting HubFirewallNetwork Problem GraphRouting HubFirewallNetwork Problem GraphRouting HubFirewallNetwork Problem GraphDevice HubGaming NetworkNetwork Problem GraphDevice HubGaming NetworkNetwork Problem GraphRouting HubGaming NetworkNetwork Problem GraphRouting HubGaming NetworkNetwork Problem GraphProtocol HubGaming NetworkNetwork Problem GraphRouting HubGatewayNetwork Problem GraphRouting HubGatewayNetwork Problem GraphDNS HubVLANNetwork Problem GraphRouting HubHome NetworkNetwork Problem GraphRouting HubHome NetworkNetwork Problem GraphError HubRouterNetwork Problem GraphProtocol HubHTTP/2Network Problem GraphProtocol HubHTTP/2Network Problem GraphProtocol HubHTTP/3Network Problem GraphProtocol HubHTTP/3Network Problem GraphProtocol HubICMPNetwork Problem GraphProtocol HubICMPv6Network Problem GraphRouting HubMulticastNetwork Problem GraphDevice HubMulticastNetwork Problem GraphRouting HubImmortalWrtNetwork Problem GraphRouting HubImmortalWrtNetwork Problem GraphDevice HubImmortalWrtNetwork Problem GraphDevice HubVLANNetwork Problem GraphRouting HubCGNATNetwork Problem GraphDevice HubIPv4Network Problem GraphDNS HubIPv6Network Problem GraphError HubIPv6Network Problem GraphRouting HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphRouting HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphProtocol HubIPv6Network Problem GraphRouting HubIPv6Network Problem GraphRouting HubiStoreOSNetwork Problem GraphDevice HubiStoreOSNetwork Problem GraphDevice HubiStoreOSNetwork Problem GraphRouting HubiStoreOSNetwork Problem GraphError HubLANNetwork Problem GraphDevice HubDockerNetwork Problem GraphRouting HubLinuxNetwork Problem GraphError HubLinuxNetwork Problem GraphDevice HubmacOSNetwork Problem GraphDevice HubmacOSNetwork Problem GraphError HubmDNSNetwork Problem GraphDevice HubmDNSNetwork Problem GraphDevice HubMesh Wi-FiNetwork Problem GraphProxy HubAI APINetwork Problem GraphProxy HubAI NetworkNetwork Problem GraphDNS HubMihomoNetwork Problem GraphProxy HubGaming NetworkNetwork Problem GraphDNS HubMosDNSNetwork Problem GraphDNS HubMosDNSNetwork Problem GraphDNS Hubmwan3Network Problem GraphRouting Hubmwan3Network Problem GraphRouting Hubmwan3Network Problem GraphRouting Hubmwan3Network Problem GraphDevice HubNASNetwork Problem GraphDevice HubNASNetwork Problem GraphDNS HubNASNetwork Problem GraphDevice HubNASNetwork Problem GraphDevice HubNASNetwork Problem GraphDevice HubNASNetwork Problem GraphDevice HubNASNetwork Problem GraphRouting HubNATNetwork Problem GraphRouting HubNATNetwork Problem GraphRouting HubNATNetwork Problem GraphRouting HubFirewallNetwork Problem GraphRouting HubFirewallNetwork Problem GraphProxy HubAI NetworkNetwork Problem GraphDNS HubNikkiNetwork Problem GraphProxy HubNikkiNetwork Problem GraphError HubNTPNetwork Problem GraphProtocol HubNTPNetwork Problem GraphProxy HubOpenClashNetwork Problem GraphDNS HubOpenClashNetwork Problem GraphProxy HubOpenClashNetwork Problem GraphProxy HubOpenClashNetwork Problem GraphProxy HubOpenClashNetwork Problem GraphRouting HubOpenWrtNetwork Problem GraphDNS HubdnsmasqNetwork Problem GraphRouting HubOpenWrtNetwork Problem GraphRouting HubSQMNetwork Problem GraphDevice HubPassWallNetwork Problem GraphDNS HubPassWallNetwork Problem GraphProxy HubPassWallNetwork Problem GraphProxy HubPassWallNetwork Problem GraphProxy HubPassWallNetwork Problem GraphProtocol HubMTUNetwork Problem GraphDevice HubPhoneNetwork Problem GraphDNS HubPi-holeNetwork Problem GraphDevice HubPlayStationNetwork Problem GraphProtocol HubPPPoENetwork Problem GraphRouting HubPPPoENetwork Problem GraphRouting HubPPPoENetwork Problem GraphRouting HubPPPoENetwork Problem GraphRouting HubIPv4Network Problem GraphProxy HubProxyNetwork Problem GraphProtocol HubQUICNetwork Problem GraphProtocol HubQUICNetwork Problem GraphRouting HubGaming NetworkNetwork Problem GraphDNS Hubsing-boxNetwork Problem GraphProxy Hubsing-boxNetwork Problem GraphProxy Hubsing-boxNetwork Problem GraphProxy Hubsing-boxNetwork Problem GraphProxy HubGaming NetworkNetwork Problem GraphDNS HubSmartDNSNetwork Problem GraphDNS HubSmartDNSNetwork Problem GraphDevice HubSteamNetwork Problem GraphDevice HubNintendo SwitchNetwork Problem GraphDevice HubAI NetworkNetwork Problem GraphProxy HubTailscaleNetwork Problem GraphProxy HubTailscaleNetwork Problem GraphProxy HubTailscaleNetwork Problem GraphDNS HubTailscaleNetwork Problem GraphProxy HubTailscaleNetwork Problem GraphProxy HubTailscaleNetwork Problem GraphProtocol HubMSSNetwork Problem GraphError HubTCPNetwork Problem GraphProtocol HubTCPNetwork Problem GraphError HubTCPNetwork Problem GraphError HubTCPNetwork Problem GraphError HubTLSNetwork Problem GraphError HubTLSNetwork Problem GraphProxy HubTUNNetwork Problem GraphProtocol HubUDPNetwork Problem GraphDNS HubUnboundNetwork Problem GraphDNS HubUnboundNetwork Problem GraphRouting HubUPnPNetwork Problem GraphRouting HubUPnPNetwork Problem GraphRouting HubVLANNetwork Problem GraphProxy HubVPNNetwork Problem GraphRouting HubDHCPNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDNS HubWi-FiNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDevice HubWi-FiNetwork Problem GraphDevice HubWindowsNetwork Problem GraphDevice HubWindowsNetwork Problem GraphProxy HubWireGuardNetwork Problem GraphProxy HubWireGuardNetwork Problem GraphDNS HubWireGuardNetwork Problem GraphProxy HubWireGuardNetwork Problem GraphProxy HubWireGuardNetwork Problem GraphProxy HubWireGuardNetwork Problem GraphDevice HubXboxNetwork Problem GraphDevice HubXboxNetwork Problem GraphProxy HubZeroTierNetwork Problem GraphShadowrocket规则Split TunnelSaaS社区报告来源可追溯社区报告来源可追溯社区报告来源可追溯补充更新:先判断问题属于 DNS、路由、分流还是 TUN
简答:搜索 DNS、路由与 TUN 配置时,先按现象选择配置层:能解析但连不上,优先查路由与出站;只有部分应用生效,优先查系统代理或 TUN 接管;域名解析异常,先查 DNS 入口、上游与缓存。随后在搜索框使用多个关键词,页面按 AND 逻辑同时匹配这些词。
定义:DNS 负责把域名解析为地址,路由决定数据包走哪条路径,分流决定不同目标使用哪个出站,TUN 则通过虚拟网卡接管系统或指定范围的流量。
先试这一步:按现象选择搜索关键词
不要一开始同时修改 DNS、默认路由和 TUN。先记录现象,再用“现象 + 配置层 + 平台”搜索,例如 DNS OpenWrt、TUN Windows、IPv6 路由 或 MTU 断流。页面原有搜索支持多个词同时匹配,输入多个词后,结果会缩小到同时包含这些关键词的文章。
| 你看到的现象 | 优先搜索 | 第一检查对象 |
|---|---|---|
| 域名解析失败、解析到错误地址 | DNS 解析、DHCP DNS | 客户端实际使用的 DNS、上游服务器、缓存和搜索域 |
| 能解析,但连接超时或走错出口 | 路由 分流 出站 | 默认路由、目标网段、规则顺序和最终出站 |
| 浏览器能用,命令行或其他应用不能用 | 系统代理 WinHTTP、TUN | 应用是否读取系统代理,以及 TUN 是否接管该进程流量 |
| 开启 TUN 后局域网、虚拟机或容器异常 | TUN 局域网、TUN 路由表 | 自动路由、严格路由、接口排除和回环路径 |
| 只有部分网站卡住、上传失败或连接中途断开 | MTU MSS 断流 | 路径 MTU、隧道额外开销和是否存在 PMTUD 黑洞 |
对于 OpenWrt,策略路由通常适合按接口、子网、IP、端口等条件选择路由表;PBR 文档还说明,它可以通过被动观察局域网 DNS 响应学习域名对应地址,并可与 dnsmasq、unbound 或 AdGuard Home 配合。查看 OpenWrt PBR 官方文档
DNS、路由、分流与 TUN 的先后关系
- DNS 查询入口:先确认请求由系统 DNS、浏览器安全 DNS、客户端内置 DNS,还是局域网网关接收。
- DNS 解析结果:确认上游、回退、缓存和 IPv4/IPv6 查询策略。DNS 规则可以按域名、查询类型、IP 版本等条件选择服务器或动作;sing-box 官方文档将 DNS 服务器、规则、默认服务器和解析策略分开定义。查看 sing-box DNS 官方文档
- 路由匹配:根据目标域名、目标 IP、端口、来源网段或进程等条件匹配规则,并确定最终出站。规则顺序很重要,排障时应先看日志中的命中规则,再看出站是否可达。
- TUN 接管:TUN 创建虚拟接口;自动路由决定哪些目标被导入该接口,严格路由还可能阻止不支持或未匹配的网络直接绕过。Mihomo 文档将
auto-route、strict-route、dns-hijack和auto-detect-interface分别列为独立配置项。查看 Mihomo TUN 官方文档 - 实际出站:客户端自身发起的 DNS、测速、规则更新或节点连接也要有明确的物理出口,否则可能出现 TUN 回环。Xray 官方文档建议使用
autoOutboundsInterface绑定实际网络接口,避免出站再次进入 TUN。查看 Xray TUN 官方文档
因此,“能解析”不等于“能连接”,“TUN 已启动”也不等于“所有应用都已被接管”。排查时应按 DNS、路由规则、TUN 路由、出站接口的顺序逐层验证。
搜索后如何照做:最小可用基线与验证命令
进入具体文章前,先建立一个可回滚的基线:保存当前客户端配置,记录默认网关、DNS、接口名称和已有代理设置;然后一次只改一个变量。每次修改后关闭并重新打开受影响的应用,再记录结果。
- Windows:运行
ipconfig /all查看网卡、默认网关和 DNS;运行route print查看 IPv4/IPv6 路由;PowerShell 中使用curl.exe验证命令行连接,避免把 PowerShell 别名误认为传统 curl。 - macOS:运行
ifconfig查看接口,运行route -n get default查看默认路由,运行scutil --dns查看系统 DNS 状态。若客户端创建了 TUN,还要确认虚拟接口名称和默认路由是否发生变化。 - Linux:运行
ip addr查看接口和地址,运行ip route查看路由,运行resolvectl status查看 systemd-resolved 的 DNS 状态;若使用策略路由,再检查ip rule和对应路由表。 - 先测直连,再测接管:先关闭 TUN 或系统代理,确认基础网络可用;再只启用 DNS;最后启用路由规则和 TUN。这样可以判断故障是在基础网络、解析、规则还是接管层。
- 检查回环:如果开启 TUN 后客户端自身连接失败,优先检查出站接口绑定、默认接口和自动路由。sing-box 官方文档说明,
auto_route应配合自动检测接口、默认接口或出站绑定接口来避免流量回环。查看 sing-box TUN 官方文档
如果要测 MTU,在 Windows 使用 ping -f -l 数值 目标主机,逐步调整数值;成功负载值加 28 字节才是 IPv4 MTU。目标主机应能响应 ICMP。测得结果只代表当前路径和当前时间,不应直接当作所有网络的固定值。
系统代理、TUN、透明代理与 FakeDNS 怎么区分
| 方式 | 主要接管范围 | 适合先排查什么 | 常见限制 |
|---|---|---|---|
| 系统代理 | 读取系统代理设置的应用 | 浏览器、支持 HTTP 或 SOCKS 的应用 | 命令行、后台服务或不读取系统代理的应用可能不生效 |
| TUN | 通过虚拟网卡接管系统或指定范围流量 | 需要覆盖更多应用、UDP 或不支持代理设置的程序 | 可能影响局域网、虚拟机、容器、IPv6 和系统 DNS |
| 透明代理 | 由路由器或系统防火墙重定向流量 | 家庭网关、OpenWrt 和多设备接入 | 依赖防火墙、策略路由、DNS 和回程路径协同 |
| FakeDNS 或 FakeIP | 用合成地址代表域名,再由客户端保存域名与地址的映射 | 需要按域名恢复规则匹配的场景 | 地址池可能与局域网、容器或办公网段冲突,排障时不能把合成地址当作真实公网地址 |
不同内核字段不能直接混用。例如 Xray TUN 使用 autoSystemRoutingTable 和 autoOutboundsInterface,sing-box 使用 auto_route、strict_route 和 auto_redirect,Mihomo 则使用 auto-route、strict-route、dns-hijack 等字段。配置前必须先打开对应内核的官方文档,按当前版本字段名核对,不要把一套配置直接复制到另一套内核。
sing-box 官方文档还说明,Linux 上的 auto_redirect 需要与 auto_route 配合,并通过 nftables 改善 TUN 路由;OpenWrt fw4 也有对应兼容处理。查看 sing-box TUN 与 auto_redirect 说明
常见报错与回滚顺序
- “解析成功但连接超时”:先记录解析出的 A/AAAA 地址,再检查目标地址是否命中正确规则、最终出站是否可用,最后检查 IPv6 默认路由和 MTU。
- “只有浏览器生效”:先确认浏览器是否读取系统代理,再用
curl.exe或终端命令分别测试;如果命令行不走代理,检查 WinHTTP 或应用自身的代理设置。 - “TUN 启动后断网”:先停用 TUN,恢复基础网络;然后检查自动路由、严格路由、DNS 劫持和客户端出站接口,最后再逐项启用。
- “局域网 NAS 或办公网段不可达”:检查私网网段是否被导入 TUN,是否需要加入路由排除或直连规则,并确认返回流量仍能回到原网关。
- “OpenWrt 域名策略不生效”:确认客户端实际使用的 DNS 是否经过路由器;再检查 PBR 是否观察到 DNS 响应、域名对应地址是否变化,以及策略是否命中正确接口。PBR 官方文档明确区分了基于域名的被动学习与直接按 IP、子网、端口匹配。查看 OpenWrt PBR 官方文档
推荐回滚顺序是:关闭 TUN → 恢复系统代理 → 恢复 DNS → 删除新增路由或策略 → 重启受影响应用。不要直接恢复出厂设置,因为这样会丢失可用于定位问题的现象和配置差异。
常见问题
搜索框输入多个关键词时,页面会怎样匹配?
多个关键词采用 AND 匹配。比如输入“OpenWrt DNS”,结果应同时包含这两个词;如果结果太少,可以先删掉平台词,再用“DNS 解析”“DNS 路由”等更宽的组合搜索。
DNS、路由和 TUN 出问题时,应该先改哪一个?
先验证基础网络和 DNS,再检查路由规则,最后启用或调整 TUN。一次只改一个变量,并在每次修改后重新测试,避免同时修改 DNS、默认路由和接管模式而无法判断原因。
为什么 TUN 已经启动,但某些应用仍然不走?
可能是自动路由没有覆盖该流量、应用使用了独立网络栈、IPv6 走了另一条路径,或严格路由与接口排除规则造成绕行。先查看系统路由和 TUN 接口,再检查客户端是否提供按进程、用户或网段的包含与排除配置。
开启 TUN 后局域网设备无法访问怎么办?
先关闭 TUN 确认局域网本身正常,再检查局域网网段是否被自动路由导入、是否缺少直连或排除规则,以及返回流量是否经过原来的网关。不要先更换 DNS,因为局域网不可达通常首先是路由或防火墙路径问题。
OpenWrt 可以按域名做策略路由吗?
可以,但实现方式取决于 PBR 和 DNS 链路。OpenWrt PBR 文档说明,PBR 本身更适合接口、子网、IP 和端口条件,同时可以被动观察局域网 DNS 响应学习域名地址;因此应同时核对 DNS 是否经过受控解析器,以及域名解析地址是否被正确学习。