I believe you've wrongly interpreted the log. Let me describe how do I
understand it.
15:45:32.035381 IP 127.0.0.1.18520 > 127.0.2.1.5353: 1536+ A (QM)?
dupaa.com. (27)
Something running on your router sends request to 127.0.2.1:5353. It's
dnscrypt there, so that most likely was a dnsmasq req
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It do can exactly that.
The configuration goes in dhcp-host statements
dhcp-host=mickey,192.168.0.10
ensures that when a DHCP request turns up from a macine idetifying
itself as "mickey", it gets given address 102.168.0.10 and
"mickey" 192.168.0.
Hi,
many thanks! - with the last two patches the build ran through.
But to be complete, two "warnings" still remain:
I'm using these options from IPFire GIT while building 'dnsmasq' (the latest
'lfs'-file and 'dnsmasq-Add-support-to-read-ISC-DHCP-lease-file.patch'
are attached, all other patche
I am building a system containing many virtual machines. Each virtual machine
will have a unique hostname, and the hostname
will be included in the domain name. The system will live on its own subnet.
The system could change over time (more machines
added to system)
I need to replicate