Closed iamobj closed 3 years ago
如题,在 fake-ip 下,这两个命令都是超时,非 fake-ip 就正常,看了一波日志,是因为在 fake-ip 下 dns 解析有问题,日志如下,有试过在 dns设置->高级设置域名黑名单,在黑名单里的域名可以正常 curl ,但是需要一个一个自己加黑名单,好麻烦,而且路由本身会请求哪些域名是个未知,只能某些功能不正常了,自己去发现再自己添加到黑名单,很麻烦,想问下作者大大是不是我哪里设置不对或者有什么操作可以解决这个问题 :grin:
OpenClash 调试日志 生成时间: 2021-01-24 00:40:06 插件版本: v0.41.14-beta 隐私提示: 上传此日志前请注意检查、屏蔽公网IP、节点、密码等相关敏感信息 #===================== 系统信息 =====================# 主机型号: Intel(R) Xeon(R) CPU E3-1265L v3 @ 2.50GHz : 1 Core 2 Thread 固件版本: OpenWrt SNAPSHOT r0-f60d3ea LuCI版本: git-20.343.54716-6fc079f-1 内核版本: 5.4.86 处理器架构: x86_64 #此项在使用Tun模式时应为ACCEPT 防火墙转发: ACCEPT #此项有值时建议到网络-接口-lan的设置中禁用IPV6的DHCP IPV6-DHCP: #此项结果应仅有配置文件的DNS监听地址 Dnsmasq转发设置: 127.0.0.1#7874 #===================== 依赖检查 =====================# dnsmasq-full: 已安装 coreutils: 已安装 coreutils-nohup: 已安装 bash: 已安装 curl: 已安装 jsonfilter: 已安装 ca-certificates: 已安装 ipset: 已安装 ip-full: 已安装 iptables-mod-tproxy: 已安装 kmod-ipt-tproxy: 已安装 iptables-mod-extra: 已安装 kmod-ipt-extra: 已安装 libcap: 已安装 libcap-bin: 已安装 ruby: 已安装 ruby-yaml: 已安装 ruby-psych: 已安装 ruby-pstore: 已安装 ruby-dbm: 已安装 kmod-tun(TUN模式): 已安装 luci-compat(Luci-19.07): 已安装 #===================== 内核检查 =====================# 运行状态: 运行中 进程pid: 49570 运行权限: 49570: cap_dac_override,cap_net_bind_service,cap_net_admin,cap_net_raw,cap_sys_resource=eip 运行用户: nobody 已选择的架构: linux-amd64 #下方无法显示内核版本号时请确认您的内核版本是否正确或者有无权限 Tun内核版本: 2021.01.01.g0ab75c5 Tun内核文件: 存在 Tun内核运行权限: 正常 Game内核版本: v0.17.0-232-ge389e33 Game内核文件: 存在 Game内核运行权限: 正常 Dev内核版本: v1.3.5-4-g6fedd7e Dev内核文件: 存在 Dev内核运行权限: 正常 #===================== 插件设置 =====================# 当前配置文件: /etc/openclash/config/self.yaml 启动配置文件: /etc/openclash/self.yaml 运行模式: fake-ip 默认代理模式: rule UDP流量转发(tproxy): 启用 DNS劫持: 启用 自定义DNS: 启用 IPV6-DNS解析: 停用 禁用Dnsmasq缓存: 启用 自定义规则: 停用 仅允许内网: 停用 仅代理命中规则流量: 启用 仅允许常用端口流量: 停用 绕过中国大陆IP: 停用 #启动异常时建议关闭此项后重试 混合节点: 停用 保留配置: 停用 #启动异常时建议关闭此项后重试 第三方规则: 停用 #===================== 配置文件 =====================# port: 7890 socks-port: 7891 allow-lan: true bind-address: "*" mode: rule log-level: silent external-controller: 0.0.0.0:9090 hosts: mtalk.google.com: 108.177.125.188 dns: enable: true listen: 127.0.0.1:7874 default-nameserver: - 114.114.114.114 - 8.8.8.8 enhanced-mode: fake-ip fake-ip-range: 198.18.0.1/16 nameserver: - 114.114.114.114 - 119.29.29.29 fallback-filter: geoip: true ipcidr: ipv6: false fake-ip-filter: - "*.lan" - time.windows.com - time.nist.gov - time.apple.com - time.asia.apple.com - "*.ntp.org.cn" - "*.openwrt.pool.ntp.org" - time1.cloud.tencent.com - time.ustc.edu.cn - pool.ntp.org - ntp.ubuntu.com - ntp.aliyun.com - ntp1.aliyun.com - ntp2.aliyun.com - ntp3.aliyun.com - ntp4.aliyun.com - ntp5.aliyun.com - ntp6.aliyun.com - ntp7.aliyun.com - time1.aliyun.com - time2.aliyun.com - time3.aliyun.com - time4.aliyun.com - time5.aliyun.com - time6.aliyun.com - time7.aliyun.com - "*.time.edu.cn" - time1.apple.com - time2.apple.com - time3.apple.com - time4.apple.com - time5.apple.com - time6.apple.com - time7.apple.com - time1.google.com - time2.google.com - time3.google.com - time4.google.com - music.163.com - "*.music.163.com" - "*.126.net" - musicapi.taihe.com - music.taihe.com - songsearch.kugou.com - trackercdn.kugou.com - "*.kuwo.cn" - api-jooxtt.sanook.com - api.joox.com - joox.com - y.qq.com - "*.y.qq.com" - streamoc.music.tc.qq.com - mobileoc.music.tc.qq.com - isure.stream.qqmusic.qq.com - dl.stream.qqmusic.qq.com - aqqmusic.tc.qq.com - amobile.music.tc.qq.com - "*.xiami.com" - "*.music.migu.cn" - music.migu.cn - "*.msftconnecttest.com" - "*.msftncsi.com" - localhost.ptlogin2.qq.com - "+.srv.nintendo.net" - "+.stun.playstation.net" - xbox.*.microsoft.com - "+.xboxlive.com" - proxy.golang.org - stun.*.* - stun.*.*.* - heartbeat.belkin.com - "*.linksys.com" - "*.linksyssmartwifi.com" #===================== 防火墙设置 =====================# #NAT chain # Generated by iptables-save v1.8.4 on Sun Jan 24 00:40:07 2021 *nat :PREROUTING ACCEPT [849:167981] :INPUT ACCEPT [788:61517] :OUTPUT ACCEPT [1295:91932] :POSTROUTING ACCEPT [1295:91932] :MINIUPNPD - [0:0] :MINIUPNPD-POSTROUTING - [0:0] :openclash - [0:0] :openclash_output - [0:0] :postrouting_lan_rule - [0:0] :postrouting_rule - [0:0] :postrouting_wan_rule - [0:0] :prerouting_lan_rule - [0:0] :prerouting_rule - [0:0] :prerouting_wan_rule - [0:0] :zone_lan_postrouting - [0:0] :zone_lan_prerouting - [0:0] :zone_wan_postrouting - [0:0] :zone_wan_prerouting - [0:0] -A PREROUTING -d 8.8.4.4/32 -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 7892 -A PREROUTING -d 8.8.8.8/32 -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 7892 -A PREROUTING -p udp -m udp --dport 53 -j REDIRECT --to-ports 53 -A PREROUTING -p tcp -m tcp --dport 53 -j REDIRECT --to-ports 53 -A PREROUTING -m comment --comment "!fw3: Custom prerouting rule chain" -j prerouting_rule -A PREROUTING -i br-lan -m comment --comment "!fw3" -j zone_lan_prerouting -A PREROUTING -p tcp -j openclash -A OUTPUT -j openclash_output -A POSTROUTING -m comment --comment "!fw3: Custom postrouting rule chain" -j postrouting_rule -A POSTROUTING -o br-lan -m comment --comment "!fw3" -j zone_lan_postrouting -A openclash -m set --match-set localnetwork dst -j RETURN -A openclash -p tcp -j REDIRECT --to-ports 7892 -A openclash_output -p tcp -m tcp --sport 1688 -j RETURN -A openclash_output -m set --match-set localnetwork dst -j RETURN -A zone_lan_postrouting -j MINIUPNPD-POSTROUTING -A zone_lan_postrouting -m comment --comment "!fw3: Custom lan postrouting rule chain" -j postrouting_lan_rule -A zone_lan_prerouting -j MINIUPNPD -A zone_lan_prerouting -m comment --comment "!fw3: Custom lan prerouting rule chain" -j prerouting_lan_rule -A zone_wan_postrouting -m comment --comment "!fw3: Custom wan postrouting rule chain" -j postrouting_wan_rule -A zone_wan_postrouting -m comment --comment "!fw3" -j FULLCONENAT -A zone_wan_prerouting -m comment --comment "!fw3: Custom wan prerouting rule chain" -j prerouting_wan_rule -A zone_wan_prerouting -m comment --comment "!fw3" -j FULLCONENAT COMMIT # Completed on Sun Jan 24 00:40:07 2021 #Mangle chain # Generated by iptables-save v1.8.4 on Sun Jan 24 00:40:07 2021 *mangle :PREROUTING ACCEPT [50077:18191562] :INPUT ACCEPT [48504:18004332] :FORWARD ACCEPT [828:66940] :OUTPUT ACCEPT [56457:23668877] :POSTROUTING ACCEPT [57289:23736761] :openclash - [0:0] -A PREROUTING -p udp -j openclash -A openclash -p udp -m udp --dport 4500 -j RETURN -A openclash -p udp -m udp --dport 500 -j RETURN -A openclash -p udp -m udp --dport 500 -j RETURN -A openclash -p udp -m udp --dport 546 -j RETURN -A openclash -p udp -m udp --dport 68 -j RETURN -A openclash -m set --match-set localnetwork dst -j RETURN -A openclash -p udp -m udp --dport 53 -j RETURN -A openclash -p udp -j TPROXY --on-port 7892 --on-ip 0.0.0.0 --tproxy-mark 0x162/0xffffffff COMMIT # Completed on Sun Jan 24 00:40:07 2021 #===================== IPSET状态 =====================# Name: localnetwork Name: common_ports Name: music #===================== 路由表状态 =====================# #route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.50.1 0.0.0.0 UG 0 0 0 br-lan 192.168.50.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan #ip route list default via 192.168.50.1 dev br-lan proto static 192.168.50.0/24 dev br-lan proto kernel scope link src 192.168.50.2 #ip rule show 0: from all lookup local 32765: from all fwmark 0x162 lookup 354 32766: from all lookup main 32767: from all lookup default #===================== 端口占用状态 =====================# tcp 0 0 :::7890 :::* LISTEN 49570/clash tcp 0 0 :::7891 :::* LISTEN 49570/clash tcp 0 0 :::7892 :::* LISTEN 49570/clash tcp 0 0 :::7893 :::* LISTEN 49570/clash tcp 0 0 :::9090 :::* LISTEN 49570/clash udp 0 0 127.0.0.1:7874 0.0.0.0:* 49570/clash udp 0 0 :::44754 :::* 49570/clash udp 0 0 :::7891 :::* 49570/clash udp 0 0 :::7892 :::* 49570/clash udp 0 0 :::7893 :::* 49570/clash #===================== 测试本机DNS查询 =====================# Server: 127.0.0.1 Address: 127.0.0.1#53 Name: www.baidu.com Address 1: 198.18.0.73 *** Can't find www.baidu.com: No answer #===================== resolv.conf.d =====================# # Interface lan nameserver 114.114.114.114 #===================== 测试本机网络连接 =====================# #===================== 测试本机网络下载 =====================# #===================== 最近运行日志 =====================# time="2021-01-23T16:12:46Z" level=info msg="Start initial rule provider China" time="2021-01-23T16:12:46Z" level=info msg="Start initial rule provider ChinaIP" time="2021-01-23T16:12:46Z" level=info msg="DNS server listening at: 127.0.0.1:7874" 2021-01-24 00:12:49 History:【self.yaml】 Restore Successful 2021-01-24 00:12:41 OpenClash Start Successful time="2021-01-23T16:18:22Z" level=info msg="Start initial provider SuYing666-Sub" time="2021-01-23T16:18:22Z" level=info msg="Start initial compatible provider MATCH" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider China" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider ChinaIP" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider Unbreak" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider Streaming" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider StreamingSE" time="2021-01-23T16:18:22Z" level=info msg="Start initial rule provider Global" time="2021-01-23T16:18:22Z" level=info msg="DNS server listening at: 127.0.0.1:7874" 2021-01-24 00:18:26 History:【self.yaml】 Restore Successful 2021-01-24 00:18:18 OpenClash Start Successful time="2021-01-23T16:20:13Z" level=info msg="Start initial provider SuYing666-Sub" time="2021-01-23T16:20:13Z" level=info msg="Start initial compatible provider MATCH" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider StreamingSE" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider Global" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider China" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider ChinaIP" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider Unbreak" time="2021-01-23T16:20:13Z" level=info msg="Start initial rule provider Streaming" time="2021-01-23T16:20:13Z" level=info msg="DNS server listening at: 127.0.0.1:7874" 2021-01-24 00:20:17 History:【self.yaml】 Restore Successful 2021-01-24 00:20:09 OpenClash Start Successful time="2021-01-23T16:21:18Z" level=info msg="Start initial provider SuYing666-Sub" time="2021-01-23T16:21:18Z" level=info msg="Start initial compatible provider MATCH" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider StreamingSE" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider Global" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider China" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider ChinaIP" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider Unbreak" time="2021-01-23T16:21:18Z" level=info msg="Start initial rule provider Streaming" time="2021-01-23T16:21:18Z" level=info msg="DNS server listening at: 127.0.0.1:7874" 2021-01-24 00:21:21 History:【self.yaml】 Restore Successful 2021-01-24 00:21:14 OpenClash Start Successful time="2021-01-23T16:21:41Z" level=info msg="Start initial provider SuYing666-Sub" time="2021-01-23T16:21:41Z" level=info msg="Start initial compatible provider MATCH" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider Unbreak" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider Streaming" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider StreamingSE" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider Global" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider China" time="2021-01-23T16:21:41Z" level=info msg="Start initial rule provider ChinaIP" time="2021-01-23T16:21:41Z" level=info msg="DNS server listening at: 127.0.0.1:7874" 2021-01-24 00:21:44 History:【self.yaml】 Restore Successful 2021-01-24 00:21:37 OpenClash Start Successful 2021-01-24 00:25:07 Reload OpenClash Firewall Rules
iptables-mod-extra依赖不正常,防火墙路由自身代理的规则未添加成功,尝试重装或者刷固件
重装依赖没用,固件是用的 lede 的,先说下环境,我是在 hyper-v 下装的,试过很多个 lede 的固件的都是这样,不过最后换成 koolshare lede 固件,问题解决
如题,在 fake-ip 下,这两个命令都是超时,非 fake-ip 就正常,看了一波日志,是因为在 fake-ip 下 dns 解析有问题,日志如下,有试过在 dns设置->高级设置域名黑名单,在黑名单里的域名可以正常 curl ,但是需要一个一个自己加黑名单,好麻烦,而且路由本身会请求哪些域名是个未知,只能某些功能不正常了,自己去发现再自己添加到黑名单,很麻烦,想问下作者大大是不是我哪里设置不对或者有什么操作可以解决这个问题 :grin: