We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.46.007-beta
Lean
Openwrt 23.05.3
Linux-arm64
Meta 内核 运行模式 Redir-Host(TUN) 禁用 QUIC IPv6 代理模式 TUN 模式
以上设置的前提下,验证发现 IPv6 下会添加 quic reject 规则到 input 链,不会添加到 forward 链
OpenClash/luci-app-openclash/root/etc/init.d/openclash
Line 2895 in e957592
Line 2481 in e957592
Line 2625 in e957592
fw3 和 fw4 都有同样的问题
Meta 内核 运行模式 Redir-Host(TUN) 禁用 QUIC IPv6 代理模式 TUN 模式 检查防火墙设置
日志无关
No response
IPv6 下使用 tun 模式也应该在 forward 链添加 quic reject 规则
The text was updated successfully, but these errors were encountered:
chore: #3863
dc14419
@vernesong 测了一下有个 bug, match-set 应该是 china_ip6_route
Line 2922 in 7256d89
Sorry, something went wrong.
这个问题是不是还没修好,我看Youtube会有类似情况
v0.46.010 已经修好了,你这个提示跟这个没关系,应该是代理本身的问题
0.46.011版本依然存在问题,表现还是卡: Tip: Firewall4 was Detected, Use NFTABLE Rules...
No branches or pull requests
Verify Steps
OpenClash Version
v0.46.007-beta
Bug on Environment
Lean
OpenWrt Version
Openwrt 23.05.3
Bug on Platform
Linux-arm64
Describe the Bug
Meta 内核
运行模式 Redir-Host(TUN)
禁用 QUIC
IPv6 代理模式 TUN 模式
以上设置的前提下,验证发现 IPv6 下会添加 quic reject 规则到 input 链,不会添加到 forward 链
OpenClash/luci-app-openclash/root/etc/init.d/openclash
Line 2895 in e957592
作为对比, IPv4 下启用 TUN,quic reject 规则只会添加 forward 链,不启用 TUN, 只会添加到 input 链
OpenClash/luci-app-openclash/root/etc/init.d/openclash
Line 2481 in e957592
OpenClash/luci-app-openclash/root/etc/init.d/openclash
Line 2625 in e957592
fw3 和 fw4 都有同样的问题
To Reproduce
Meta 内核
运行模式 Redir-Host(TUN)
禁用 QUIC
IPv6 代理模式 TUN 模式
检查防火墙设置
OpenClash Log
OpenClash Config
No response
Expected Behavior
IPv6 下使用 tun 模式也应该在 forward 链添加 quic reject 规则
Additional Context
No response
The text was updated successfully, but these errors were encountered: