Static IP Address Being "Forgotten" by NAS

WD Legacy Products My Book Live
1

I have setup my NAS with the IP address 10.0.0.10 (which is not in the scope of my DHCP Server - 10.0.0.100 to 10.0.0.199) and have confirmed the netmask, gateway and DNS server are all correct - but hours after everything is up and running, I find my NAS “forgets” it has a Static IP address set and grabs an IP Address from my DHCP Server for some reason. When I log into my NAS, I can clearly see that it is set for a Static IP address of 10.0.0.10, but it is currently using an 10.0.0.192 address (DHCP assigned). As soon as I hit save on the options pane too, it jumps back to the 10.0.0.10 Statically set address.

Here is a screenshot of the Network tab on my NAS:

Why is this happening? If it’s set for a static IP address, why is it suddenly grabbing an IP address from my DHCP server? 

2

Are you running updated firmware?   1.02.03?

3

Yes - newest firmware (1.02.03).

What’s interesting is I extracted the logs off of it and the daemon.log file it has the following:

Jan  7 17:56:48 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:56:59 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:57:11 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:57:32 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:57:47 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:05 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:19 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:34 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:45 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:46 localhost avahi-autoipd(eth0)[3101]: Found user ‘avahi-autoipd’ (UID 106) and group ‘avahi-autoipd’ (GID 109).

Jan  7 17:58:46 localhost avahi-autoipd(eth0)[3101]: Successfully called chroot().

Jan  7 17:58:46 localhost avahi-autoipd(eth0)[3101]: Successfully dropped root privileges.

Jan  7 17:58:46 localhost avahi-autoipd(eth0)[3101]: Starting with address 169.254.8.206

Jan  7 17:58:52 localhost avahi-autoipd(eth0)[3101]: Callout BIND, address 169.254.8.206 on interface eth0

Jan  7 17:58:56 localhost avahi-autoipd(eth0)[3101]: Successfully claimed IP address 169.254.8.206

Jan  7 17:58:56 localhost avahi-autoipd(eth0)[3101]: Got SIGTERM, quitting.

Jan  7 17:58:56 localhost avahi-autoipd(eth0)[3101]: Callout STOP, address 169.254.8.206 on interface eth0

Jan  7 17:58:56 localhost avahi-autoipd(eth0)[3102]: client: RTNETLINK answers: Cannot assign requested address

Jan  7 17:58:56 localhost avahi-autoipd(eth0)[3102]: Script execution failed with return value 2

Jan  7 17:58:57 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3

Jan  7 17:58:58 localhost dhclient: DHCPOFFER from 10.0.0.1

Jan  7 17:58:58 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67

Jan  7 17:58:58 localhost dhclient: DHCPACK from 10.0.0.1

Jan  7 17:58:59 localhost dhclient: bound to 10.0.0.192 – renewal in 34649 seconds.

…So something is going on.

4

Yep, DHCP deamon is definitely still running. Have you tried just resetting the NAS since you changed to static?

5

I just arrived home from work and found my NAS back on a DHCP assigned IP address. Once I restarted the device it went back on the static IP address.

We’ll see if this restart fixes anything - but I doubt it. 

6

Thank you TonyPh12345 - the DHCP Deamon seems to have been disabled after a restart. Been running it for the week with no issues. 

Cheers.