I just did a clean build of DAQ and when I ran a test to verify it was all working, I found that the ipaddr module never finishes and never times out. Here's the last log message I grabbed before cancelling it but you can see it was already running this module for well over an hour somehow ignoring testing timeouts. This new issue combined with this issue #909 makes this module unusable in it's current state.
Oct 27 23:01:34 ipaddr.ipaddr03 INFO Device 0012ea0ec36b ip notification 10.20.58.123 (long)
Oct 27 23:01:51 dhcp INFO DHCP monitor gw03 received Offer reply after 6110s: 10.20.58.159/ac:1f:6b:b4:31:ba
I just did a clean build of DAQ and when I ran a test to verify it was all working, I found that the ipaddr module never finishes and never times out. Here's the last log message I grabbed before cancelling it but you can see it was already running this module for well over an hour somehow ignoring testing timeouts. This new issue combined with this issue #909 makes this module unusable in it's current state.