mirrors/dae
1
0
Fork 0
mirror of https://github.com/daeuniverse/dae.git synced 2025-07-14 01:40:32 +07:00
Code Issues Packages Projects Releases Wiki Activity

chore: remove dnsmasq must_direct in example.dae

Browse Source
This commit is contained in:
mzz2017
2023-04-07 19:47:01 +08:00
parent 7cb71c501f
commit efacd08910
3 changed files with 2 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/getting-started/README.md
View File

@ -161,7 +161,7 @@ group {
# See https://github.com/daeuniverse/dae/blob/main/docs/routing.md for full examples.
routing {
pname(NetworkManager, systemd-resolved, dnsmasq) -> must_direct
pname(NetworkManager) -> direct
dip(224.0.0.0/3, 'ff00::/8') -> direct
### Write your rules below.

9
docs/getting-started/troubleshooting.md
View File

@ -18,14 +18,7 @@ Compile dae with CFLAG `-D__REMOVE_BPF_PRINTK`. See [build-by-yourself](build-by
**1. Troubleshoot local DNS service**
If you use `systemd-resolved`, `dnsmasq` or other local DNS service in `/etc/resolv.conf`, do not use their DNS service.
Methods to disable their DNS service:
1. Method 1: by modifying their configurations.
2. Method 2: by modifying the content of `/etc/resolv.conf` to `nameserver 223.5.5.5` or other DNS.
Alternatively, if you really want to use them, refer to [external-dns](external-dns.md).
If you use `adguardhome`, `mosdns` in `dns` section, refer to [external-dns](external-dns.md).
**2. Troubleshoot firewall**

5
example.dae
View File

@ -142,11 +142,6 @@ group {
routing {
### Preset rules.
# If you bind to WAN and set upstream (in section "dns") to a DNS service in localhost (dnsmasq, adguard, etc.),
# to avoid loops, let them "must_direct", which makes DNS requests not redirect back to dae again.
# "pname" means process name.
pname(dnsmasq, systemd-resolved) && l4proto(udp) && dport(53) -> must_direct
# Network managers in localhost should be direct to avoid false negative network connectivity check when binding to
# WAN.
pname(NetworkManager) -> direct