the syslog on my shake is full of
Dec 25 15:44:04 raspberryshake dhclient: No DHCPOFFERS received.
Dec 25 15:44:04 raspberryshake dhclient: No working leases in persistent database - sleeping.
Dec 25 15:50:38 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Dec 25 15:50:41 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Dec 25 15:50:47 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Dec 25 15:51:02 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Dec 25 15:51:10 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Dec 25 15:51:18 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
Dec 25 15:51:35 raspberryshake dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
etc
The instructions say that when a hardwired eth0 connection is found, the shake shuts off wlan0. If it is shut off, then why is the dhclient bothering to do all this stuff on wlan0?
been away for a while. I rebooted my shake in the interim due to some work on the system and it seems the syslog messages about DHCPDISCOVER have stopped.
Here is a log file from just now - although it may not show any problem.
glad to hear it’s working again. looking back in the log files, it seems that when the unit booted on 27-sep, it did not find an ethernet interface, and so was unable to assign an IP address successfully. the messages in syslog you referred to were most likely related to the system trying to get your DHCP server to get one assigned.
your latest reboot, however, does not exhibit this problem, so since there is an IP address assigned to the ethernet interface, there no further attempts to get a response from DHCP.
Hmmm - well, after the Sept reboot, it did continue to operate with the same IP address it had for the preceding year, so it’s not clear why it should keep asking for an address assignment.
I would be happy to have the unit assigned a static IP. Is that possible ? /etc/dhcpcd.conf does not look like what I am used to seeing.
have the DHCP server assign the same address based on the Shake Pi’s MAC address
use the web configuration screen (Settings::Network) to assign a static IP on the Shake Pi itself
but, it was probably just a hiccup before, so i’m not sure setting a fixed IP is absolutely necessary, especially on a large network with many computers, you will have to guarantee that your permanent IP will never conflict with any other computer on the network.