Hi!
Some more information - lease log from board after re-installation and dhcp server log:
================================
lease {
interface "eth0";
fixed-address 111.111.3.15;
option subnet-mask 255.255.252.0;
option dhcp-lease-time 7200;
option routers 111.111.1.2;
option dhcp-message-type 5;
option dhcp-server-identifier 111.111.1.2;
option domain-name-servers 111.111.1.2;
option broadcast-address 111.111.3.255;
option domain-name "
domain.fi";
renew 5 2016/03/11 14:46:10;
rebind 5 2016/03/11 15:41:49;
expire 5 2016/03/11 15:56:49;
}
lease {
interface "eth0";
fixed-address 111.111.3.15;
option subnet-mask 255.255.252.0;
option routers 111.111.1.2;
option dhcp-lease-time 7200;
option dhcp-message-type 5;
option domain-name-servers 111.111.1.2;
option dhcp-server-identifier 111.111.1.2;
option broadcast-address 111.111.3.255;
option domain-name "
domain.fi";
renew 5 2016/03/11 14:44:36;
rebind 5 2016/03/11 15:41:52;
expire 5 2016/03/11 15:56:52;
}
lease {
interface "eth0";
fixed-address 111.111.3.11;
option subnet-mask 255.255.252.0;
option routers 111.111.1.2;
option dhcp-lease-time 7200;
option dhcp-message-type 5;
option domain-name-servers 111.111.1.2;
option dhcp-server-identifier 111.111.1.2;
option broadcast-address 111.111.3.255;
option domain-name "
domain.fi";
renew 2 2016/05/17 06:39:51;
rebind 2 2016/05/17 07:37:25;
expire 2 2016/05/17 07:52:25;
}
====================
As you can see, board gets two leases pretty rapidly, then it gets NTP time and new lease with new IP. Is this problem coming from the fact that when board gets NTP time, it notices that time is over expiration time and it has to drop its lease.
