My RS4D (R9344) is no longer connecting. We changed the network to a static IP. I then logged onto the station webpage and under settings->Network-> I checked Static IP and put the IP in there and then rebooted. This broke the Shake. I then directly connected to the Shake and unchecked static IP and rebooted but I can no longer connect to the Shake. Is there anything I need to do to allow it to connect and send data?
1 Like
Hello fishynp, and welcome to the community!
I think I may know what is causing this issue. Could you please connect directly again, then log into the Shake via SSH (if needed, instructions on how to do so can be found here: How to access your Raspberry Shake’s computer via ssh ), run the following two commands:
cat /etc/dhcpcd.confcat /etc/resolv.conf
and post their output here? Thank you!
myshake@raspberryshake**:/opt $ cat /etc/dhcpcd.conf
interface eth0
static domain_name_servers=172.20.120.20
static ip_address=155.97.106.153/
static routers=
static domain_name_servers=172.20.120.20
A sample configuration for dhcpcd.
See dhcpcd.conf(5) for details.
Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel
Inform the DHCP server of our hostname for DDNS.
Use the hardware address of the interface for the Client ID.
clientid
or
Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
#duid
Persist interface configuration when dhcpcd exits.
persistent
Rapid commit support.
Safe to enable by default because it requires the equivalent option set
on the server to actually work.
option rapid_commit
A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
Most distributions have NTP support.
option ntp_servers
Respect the network MTU.
Some interface drivers reset when changing the MTU so disabled by default.
#option interface_mtu
A ServerID is required by RFC2131.
require dhcp_server_identifier
Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
A hook script is provided to lookup the hostname if not set by the DHCP
server, but it should not be run by default.
#nohook loo
Thank you fishynp, this is just what I needed.
The first lines confirm the idea I had in mind. On some occasions, due to a known bug (that will be fixed in the coming Shake OS releases), no specified static router appears in the dhcpcd.conf, and the Shake cannot find the proper gateway to reach the wider internet.
To fix this, open the file again with:
sudo nano /etc/dhcpcd.conf
Then delete all the lines starting with static:
static domain_name_servers=172.20.120.20
static ip_address=155.97.106.153/
static routers=
static domain_name_servers=172.20.120.20
And leave only interface eth0 at the start of the file. Then, save the file with the sequence:
Ctrl+X, Y, Enter
To make sure those changes took hold, restart the service with:
sudo service dhcpcd restart
And, lastly, restart the shake with sudo reboot.
Now, your Shake should be able to connect via your router. If you want to configure a Static IP again, you’ll have to do it manually, following a similar procedure. You can find detailed instructions here: Static IP.
If other issues arise, plase download the new log files, copy the new output from the dhcpcd and resolv files, and post all here.
Thank you.
That fixed it! It’s back up and running. Thanks.
2 Likes
Great to read that, happy to help!