On 2019-07-01 02:08, Geert Stappers wrote:
> On 01-07-2019 10:41, Nicolas Cavallari wrote:
>> On 26/06/2019 22:32, Geert Stappers wrote:
>>> My (educated??) guess is that lease data is stored in Dbus.
>>> My only point to back that up, is `dnsmasq -v` showing  "DBus"
>> D-Bus does not store data, it's merely an old-style RPC.
>> dnsmasq does not send any D-Bus message when giving out leases, it merely
>> provides an API to add/remove them while it is running.
>> Without any lease file or lease script, dnsmasq has no way to have a memory 
>> of
>> the lease.
>> maybe it's just the client sending a DHCPREQUEST directly with the old lease,
>> and dnsmasq being to eager to give it out ?
> A network sniff (  tcpdump / tshark / wireshark )  would be helpfull
> Cheers
> Geert Stappers
> Willing to analyze a  libpcap network sniff file.

I'll have to do a tcpdump on it at some point.  But the device can't
remember the old lease (it doesn't store it in nonvolatile memory) so it
should ask like new.

Dnsmasq-discuss mailing list

Reply via email to