Ekko
Ekko
修改 嗅探超时 (ms) 为 200 后比较稳定的能成功了 root@ImmortalWrt:~# ping 192.168.33.120 PING 192.168.33.120 (192.168.33.120): 56 data bytes 64 bytes from 192.168.33.120: seq=0 ttl=64 time=0.967 ms 64 bytes from 192.168.33.120: seq=1 ttl=64 time=1.273...
刚好现在有可以复现的场景,是否需要获取更多环境的信息来找根本的原因?或者需不需要跑什么测试代码
#### UPDATE! DoH3 scheme is h3 now time="Sep 24 17:15:26" level=trace msg="Received UDP(DNS) 192.168.33.244:52874 192.168.33.1:53: wq.io. A" time="Sep 24 17:15:26" level=trace msg="Request to DNS upstream" question=[{wq.io. 1 1}] upstream="h3://dns.alidns.com:443" time="Sep...
Both h3 and http3 can be DoH3's scheme now
I do not change the behavior of TCP dns and I just tested it works well ``` time="Sep 25 02:59:13" level=trace msg="Received UDP(DNS) 192.168.33.244:50348 192.168.33.1:53: wq.io. A" time="Sep 25 02:59:13"...
Since DoH3 is broken by FakeNetPacketConn's implementation, I have forked the outbound package and temporary disable some code about quic.OOBCapablePacketConn implement, If you have any conclusions about this issue, please...
``` time="Sep 25 17:03:19" level=trace msg="Request to DNS upstream" question=[{wq.io. 1 1}] upstream="quic://dns-unfiltered.adguard.com:853" time="Sep 25 17:03:19" level=trace msg="Choose DNS path" choose="udp+4" ipversions=[4 6] l4protos=[udp] upstream="quic://dns-unfiltered.adguard.com:853" use="94.140.14.140:853" time="Sep 25 17:03:21" level=trace...
@douglarek DoQ should work with alidns now
> dae version unstable-20240926.pr-649.r17.bc5204 x86_64 > > Doh upstream https://cloudflare-dns.com/dns-query > > [Sep 26 03:14:38] WARN handlePkt: Post "https://104.16.248.249:443/dns-query": tls: failed to verify certificate: x509: certificate is valid for 1.0.0.1,...
ODoH is too hard to find a proxy server, I give up to implement it, for guys who interest in DNS protocol like ODoH or DNS protocol has similar approach,...