unRAID Server Basic

version: 5.0-beta12

----------------------------

This is from the System Log (and is only a VERY small portion)

----------------------------

Dec  7 09:58:41 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 10:58:41 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 10:58:41 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

Dec  7 10:58:41 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 11:58:41 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 11:58:41 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

Dec  7 11:58:41 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 12:58:41 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 12:58:41 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

Dec  7 12:58:41 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 13:58:42 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 13:58:42 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

Dec  7 13:58:42 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 14:58:42 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 14:58:42 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

Dec  7 14:58:42 Tower dhcpcd[881]: eth0: leased 192.168.14.20 for 7200 seconds

Dec  7 15:58:42 Tower dhcpcd[881]: eth0: renewing lease of 192.168.14.20

Dec  7 15:58:42 Tower dhcpcd[881]: eth0: acknowledged 192.168.14.20 from 192.168.14.1

 

Interesting that the lease is granted for two hours and that the server appears to be renewing the lease every hour.

 

The two hour lease is part of the problem.  Is the lease time set this way in your router for a reason?  It is quite common to set leases to longer periods, 24 hours, a week, or longer, and that will generally not cause any problems.  Take a look at the DHCP settings in the router.

 

You could consider assigning a static address to the server so that it did not need to issue any DHCP requests.

Setting a static DHCP reservation in the router for the severs MAC address is preferable to static addressing for configuration management.

True - provided that the router supports that feature.  Some don't, many do.  But the lease time still has an effect and two hours is still relatively short unless there are many devices joining and leaving the network.

I would set it static either way.

Playing even with older routers you can normally set a range of what is static (reserved) and what is dhcp. If possible set your ip of your unRAID in a range that is reserved and set a range for DHCP.

 

Also look at your router and see if you set something for how long a lease period is.