connection.private_address Device does not have active lease

[duncangreene]

Conducted a test on this device.

Test result here.

With an eye on the above "Device does not have active lease" text, looking at the connection.pcap, was it actually the case that the DUT did have an active lease, but it had not lapsed/released its 10.10.10.14 lease as it should have?

Is this interpretation correct? If so, could this be communicated in the report as such?

[duncangreene]

A separate device (Samsung QM85) also presented similar failure on connection.private_address to the above. I haven't studied the Wireshark trace, but posting on this issue in case it turns out to be useful/related.

Samsung QM85 v1080.zip