Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

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

[Support Request] openwrt上运行成功, 就是好奇几个点 #476

Closed
3 tasks done
minkoonim opened this issue Mar 11, 2024 · 1 comment
Closed
3 tasks done

[Support Request] openwrt上运行成功, 就是好奇几个点 #476

minkoonim opened this issue Mar 11, 2024 · 1 comment

Comments

@minkoonim
Copy link

Checks

  • I have searched the existing issues
  • I have read the documentation
  • Is it your first time sumbitting an issue

Support Request

我参考了 #79, 把DNSMASQ 默认"重定向"关了, 意思是要不是这样, DAE 和 DNSMASQ 互相争取抓取 DNS QUERY 的 UDP REQUEST嘛?

我的 DNS.DAE 按官方配置模板设置,
就把 google 和 ali 的 smartdns的两个口, 换成127.0.0.1:6053(替代谷歌), 127.0.0.1:6054(替代阿里),

upstream {
  overseas: 'udp://127.0.0.1:6053'
  china: 'udp://127.0.0.1:6054'
}

routing {
  request {
    qname(ext:'geosite.dat:category-ads') -> reject
    qname(ext:'geosite.dat:category-ads-all') -> reject
    qname(geosite:cn) -> china
    fallback: overseas
  }
  
  response {
    upstream(overseas) -> accept
    # Possibly polluted, re-lookup using overseas.
    ip(geoip:private) && !qname(geosite:cn) -> overseas
    fallback: accept
  }
}

我在这好奇的是
我按 1 修改INIT.D之前,
试过dnsmasq的接听口改了0 (让他不要听53), 这时DNS QUERY 全失败.
反而让他听53口, 就能nslookup成功, 而且显示的 smartdns服务器名称.

  1. 如果机场不支持IPV6, 而QUERY RESULT有IPV6 地址,
    DAE会觉得不能进, 然后发生 (tcp6) no alive dialer 是吗?

Current Behavior

No response

Expected Behavior

No response

Steps to Reproduce

No response

Environment

  • Dae version (use dae --version):
    can't find dae, using daed-next,
    daed-next version 2023-12-02-102cb56-core-2024-03-07
  • OS (e.g cat /etc/os-release): openwrt 23.05.2
  • Kernel (e.g. uname -a): 6.6.21
  • Others: using daed-next

Anything else?

No response

@dae-prow
Copy link
Contributor

dae-prow bot commented Mar 11, 2024

Thanks for opening this issue!

@daeuniverse daeuniverse locked and limited conversation to collaborators Sep 28, 2024
@MarksonHon MarksonHon converted this issue into discussion #662 Sep 28, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant