Thank you Marco,
from the logs of the working one (RCF63
), with IP address: 10.254.181.154
, it appears that the router has managed to assign a proper DNS address, that allows internet communication (10.254.181.153
).
For some reason, this is not happening with the new one (R4F07
), with IP address: 10.254.181.155
, even if it’s connected to the same network, because the assigned DNS address is a strange 192.168.8.1
, which is a local address completely different from what your router seems to assign.
Thus, I would manually update the DNS address of the not working Shake with the same one of the working one. Here’s a brief guide:
https://manual.raspberryshake.org/firewallIssues.html#how-to-manually-change-dns , to see if this solves the issue. I’ll add some more info below.
There are two possible ways: setting a manual IP and DNS in the http://rs.local web config, or adding a line to /etc/dhcpcd.conf
in the Shake filesystem.
- The first doesn’t require logging into the Shake. Navigate to
rs.local
, make note of the Shake’s IP address, then click on the Settings
gear icon (high on the left) to access the configuration menu.Click on NETWORK, then under ETHERNET SETTINGS, click on “Enable static IP”.Fill out the Static IP field with the address you copied from the front page.Fill out the DNS server field with a more reliable DNS service or the one of your choice.
This could solve your issue, bypassing the modem/router settings and going straight to the internet.
The second way, a bit more complex, in which you can keep your Shake on a dynamic IP (assigned by your modem/router):
- SSH into the Shake (guide here: How to access your Raspberry Shake’s computer via ssh — Instructions on Setting Up Your Raspberry Shake)Once you’re in, copy and paste these commands (this example is for Cloudflare DNS):
sudo echo 'static domain_name_servers=1.1.1.1 1.0.0.1' >> /etc/dhcpcd.conf
sudo service dhcpcd restart
Now make sure those changes took hold:
nano /etc/resolv.conf
The file should look like the following:
# Generated by resolvconf
nameserver 1.1.1.1
nameserver 1.0.0.1
You should not need to restart, these changes will take effect immediately, but if you want, you can still do it.