[ArjenR49]

Is there a way to retrieve the value of the additional DNSMasq option
server=192.168.x.abc

There are several nvram variables which contain the correct value, but all look like they are 'derived', e.g.
ath1.1_dns_ipaddr=192.168.5.60

Executing
nvram show | grep server
in an ssh session, will give me
...
# PiHole DNS server
server=192.168.5.60
server=fe80::6b0a:7473:53ae:761c
...
which are a few lines from my Additional DNSMasq options field.
(obviously having two server= options likely means that 'server' cannot be an nvram or memory variable as such)

echo $server gives me an empty line, just as
echo $(nvram get server).

root@R7800:~# echo $server

root@R7800:~# echo $(nvram get server)

root@R7800:~# echo $(nvram get br2_dns_ipaddr)
192.168.5.60
would be ok, but br2_dns_ipaddr is 'derived' from the original setting somehow and I may not always have a br2, nor br1.
However, br0_dns_ipaddr, which I assume would always be present, does not exist ...

In my firewall script I was able to use:
ROUTER_IP=$(nvram get lan_ipaddr)
and refer to that variable in the actual rules, and that's the kind of thing I'd like to do for DNS IP as well.

[Alozaros]

if i got you correctly...my 2 cents

by default DNSmasq serves all interfaces...but if you specify interface it gets more specific..
interface=br0 so you can add interface= to all interfaces you want to mention only...

to find witch servers are in use
cat /proc/net/ip_conntrack | grep 'dport=53 '
cat /tmp/resolv.dnsmasq - shows DNSmasq serves used too..
or any other port you've chosen (this command might not work on all routers)

to see DNSmasq cache entries- cat /tmp/DNSCache.log

but you have to activate the logging in DNSmsaq

cat /tmp/dnsmasq.conf - shows DNSmsaq config

another one more advanced command for high grade routers

cat /proc/net/ip_conntrack | grep -Eo "^udp [^s]*src=$(nvram get wan_ipaddr) .*" | grep -Eo '^.*dport=53 ' | sort -k3,3rn

[eibgrad]

Anything specified in the Additional DNSMasq Options field ultimately ends up in the DNSMasq config file, so you can just grep that file rather than searching nvram (which can sometimes be difficult given the way things are encoded).

[ArjenR49]

I haven't had too much time to try the commands Alozaros proposed, but also from earlier experience I knew that there's no such file on my R7800 as ip_conntrack. Instead I found a file called np_conntrack, which looks like it contains similar information (on which the active connections table seems to be based).

The most elaborate command
cat /proc/net/ip_conntrack | grep -Eo "^udp [^s]*src=$(nvram get wan_ipaddr) .*" | grep -Eo '^.*dport=53 ' | sort -k3,3rn
I couldn't get to produce anything even after changing the filename. I then tried it up to and including the first grep, but no dice. There are no lines starting with udp in that file.
And then it was time for bed ...
after noticing the latest 44044 had been pulled and checking if the problem with that build may concern the R7800, too.

[egc]

try filename is nf_conntrack (depending on Kernel version (I think) it is ip_conntrack or nf_conntrack)

[eibgrad]

Older systems, it's ip_conntrack. Newer systems, ip_conntrack has been deprecated in favor of nf_conntrack. Output of each is very similar, but different enough that that watch command (which looks like it's mine) probably needs some minor modifications.

[yoyoma2]

Have you tried variable dnsmasq_options? That's what easyddup uses to save/restore "Additional Dnsmasq Options".

[ArjenR49]

[yoyoma2]

Try these two:

For ipv4: