OpenWRT-- bind: address already in use

[d3nteoomph]

Hi,
I cannot use the 0.0.0.0:53 in 'listen_addresses'
I wanted to use it because of monitoring UI, to see what IP asking DNScrypt to resolve a domain.
So now I see in 'Recent Queries' only 127.0.0.1, but I want to see an IPs from my local network
I tried to stop Dnsmasq and then run DNSCrypt - It worked,but dnsmasq constantly sending a lot of errors after run
What can I do to see real ips of clients in DNSCrypt monitor and do not bother dnsmasq?
sorry for my bad eng...

[jedisct1]

What you are seeing is expected.

dnscrypt-proxy can only display the address of the client that is directly connected to it. In your current setup, that client is dnsmasq, so the Monitoring UI shows 127.0.0.1 (or the router local address), not the original LAN host.

The bind: address already in use error is also expected if dnsmasq is already listening on port 53. Both services cannot bind to 0.0.0.0:53 at the same time.

So there are really two possible setups:

1. dnsmasq listens on :53 and forwards to dnscrypt-proxy - works fine - but dnscrypt-proxy only sees dnsmasq as the client

2. dnscrypt-proxy listens on :53 directly - then the Monitoring UI can show real LAN client IPs - but dnsmasq must no longer own port 53

3. If your goal is to see real client IPs in dnscrypt-proxy, clients must query dnscrypt-proxy directly. On OpenWrtthat usually means moving dnsmasq off port 53, or disabling its DNS listener and keeping it only for DHCP/local-name duties.

Also make sure:

[monitoring_ui]
enable_query_log = true
privacy_level = 0

Otherwise client IPs will still be hidden or anonymized.

So in short: this is not something dnscrypt-proxy can recover when dnsmasq is in front of it; the original client IP is already lost at that point.

[d3nteoomph]

Thank you for the answer!
Is there any cons when Dnscrypt proxy listens on 53 port directly?