[Bug Report] Version 0.5.0 does not work when using an external dns service. #412
Comments
|
Thanks for opening this issue! |
|
Hi, would you care to give #414 a shot? You can download statically linked binary from https://github.com/daeuniverse/dae/actions/runs/7431631804 |
|
@jschwinger233 I have observed something very strange in this version. My configuration is as follows, I apologize if it's a configuration problem |
|
For additional information, my router system is VyOS, the kernel has been recompiled according to dae requirements, the DNS service is Technitium DNS. |
|
@hyunrealshadow Can I see dae's log for IPv4 DNS failure? |
|
@jschwinger233 Some of the logs are as follows, I don't see failures related to ipv4 |
|
@hyunrealshadow You already tried #414 but still failed on IPv4 DNS, right? Can you set log level to |
|
@jschwinger233 Use #414 before ipv6 dns doesn't work, #414 ipv4 dns doesn't work |
|
@hyunrealshadow Really appreciate! I just pinpointed a bug thanks to your log, and pushed another commit to #414: f1c2111 Would you like to download the latest build and try again? |
|
@jschwinger233 Unfortunately, I tried the latest version and it still doesn't work |
|
@hyunrealshadow thanks! It looks like DNS reply was dropped by kernel as no errors were found from dae. I wish I could reproduce the case on my environment 🫠 |
|
BIG kudos to @hyunrealshadow who recompiled his or her kernel for tracing, with patience to run all the commands I asked for. |
|
@hyunrealshadow Would you like to try #414 again? I queued a commit (e447d24) to solve L2 problems. |
|
Thank you so much @jschwinger233 for #414! |
|
Thanks @hyunrealshadow ! Still, I don't know if #414 fixes the original issue: @BOBINIUNIU would you like to try the PR build? |
I pulled the code from this branch and recompiled the new version, unfortunately it still doesn't work. Log |
nft 'insert rule inet firewalld filter_INPUT mark 0x08000000 accept'
nft 'insert rule inet fw4 input mark 0x08000000 accept'Execute the above commands and try again. |
root@pve:~# nft 'insert rule inet firewalld filter_INPUT mark 0x08000000 accept' root@pve:~# nft 'insert rule inet fw4 input mark 0x08000000 accept' |
|
@BOBINIUNIU nft list ruleset |
Still no luck root@pve: root@pve:~# nft 'insert rule inet fw4 input mark 0x08000000 accept' |
|
@BOBINIUNIU 你是 debian 吗，有防火墙吗 |
PVE 直接安装， 内核版本Linux 6.5.11-4-pve，防火墙关闭 |
我们没有类似的环境，可以有你的联络方式吗（telegram 或者 email，可以直接发送到我的邮箱 [email protected]） |
PVE也是使用的Debian内核。我在Debian 12下测试也是相同的结果。我可以把coredns和dae的配置文件都发给你测试 |
|
@BOBINIUNIU 好的，我来试一下能不能复现 |
所有文件已发送到你的邮箱，请查收 |
我没有收到你的邮件，垃圾箱也是空的 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
@BOBINIUNIU 我们新修了一个问题，你可以再试试 #422 的最新 commit 吗 |
mzz2017
changed the title
|
问题已修复，感谢各位的辛勤工作。 |
|
问题仍然没有完全修复，重启动一次后问题再次出现了 |
|
@BOBINIUNIU 不知道是不是同一个问题，你可以： 创建一个文件 |
|
不过你的这个日志应该不是这个问题，你看看你的 dns server 有没有监听 53？ sudo lsof -i:53 |
|
我昨天的测试流程有误，仅仅重启了服务而未重启系统清理DNS缓存。问题实际上没有修复。 53端口 99-sysctl.conf |
|
两种方法均无效。所有配置文件都发给了mzz2017，应该是可以重现这个问题吧 |
|
更多测试 直连的DNS是正常的，通过代理发送的DOH请求全部无法工作 1.1.1.1/dns-query |
这是你的 socks5 服务器（dae 连接的那个节点）不支持 udp，正常报错。 |
Checks
Current Behavior
Version 5.0 does not work when using an external dns service. version 4.0 works fine.
-------------------------Log--------------------------
Jan 04 22:50:39 pve dae[1493]: level=info msg="192.168.1.6:59156 <-> 127.0.0.1:53" _qname=yahoo.com. dialer=direct dscp=0 mac="58:47:ca:72:64:15" network="udp4(DNS)" outbound=direct pid=0 >
Jan 04 22:50:41 pve dae[1493]: level=info msg="192.168.1.6:59158 <-> 127.0.0.1:53" _qname=yahoo.com. dialer=direct dscp=0 mac="58:47:ca:72:64:15" network="udp4(DNS)" outbound=direct pid=0 >
Jan 04 22:50:41 pve dae[1493]: level=info msg="192.168.1.79:59322 <-> 127.0.0.1:53" _qname=f-vali.cp31.ott.cibntv.net. dialer=direct dscp=0 mac="7a:1b:06:73:2c:0d" network="udp4(DNS)" outb>
Jan 04 22:50:42 pve dae[1493]: level=warning msg="handlePkt: failed to read from: 127.0.0.1:53 (dialer: direct): read udp [::]:45345: i/o timeout"
Expected Behavior
No response
Steps to Reproduce
No response
Environment
dae --version):cat /etc/os-release):uname -a):Anything else?
global {
log_level: error
lan_interface: enp2s0
wan_interface: enp2s0
allow_insecure: false
dial_mode: domain
}
node {
root_node: 'socks5://127.0.0.1:10000'
cloud_node: 'socks5://127.0.0.1:10001'
}
group {
root_group {
policy: fixed(0)
}
}
dns {
upstream {
coredns: 'udp://127.0.0.1:53'
}
routing {
request {
fallback: coredns
}
}
}
routing {
pname(coredns) && l4proto(udp) && dport(53) -> must_direct
pname(naive) -> must_direct
dport(53) -> direct
The text was updated successfully, but these errors were encountered: