Is there a way of using Shake with Plusnet as my connection does not support port forwarding.
You do not need port forwarding. There is no incoming connection to handle. All connections are outbound.
1 Like
I have been running my new raspberry shake kit now for three weeks and restarted it sevral times but still not connected to network. I supplied my own raspberry 3B+ and it appears to be working as it is gathering and storing Helicorder data. The other problem is although I have used the same email address for local and shake net I have still not been recognized. Here is the latest log.
RSH.RF3AC.2024-04-29T09 02 34.logs.tar (2.3 MB)
Hello David, and thank you for your logs.
The Shake boots up without issues, as you have seen, but it cannot seem to find a proper DNS server:
2024 116 21:40:11: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
Thus, it doesn’t connect to our RS servers, and for this reason, you cannot see it on our apps and on ShakeNet when you log in with the same email.
Could I please ask you to SSH into the Shake (instructions here: How to access your Raspberry Shake’s computer via ssh — Instructions on Setting Up Your Raspberry Shake ), execute the following two commands:
cat /etc/dhcpcd.confcat /etc/resolv.conf
and post their output here? Thank you!
-
cat /etc/dhcpcd.confresults in
interface eth0
static ip_address=192.168.192.192/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.192/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.192/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.192/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.192/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.40/
static routers=
static domain_name_servers=1.1.1.1
static ip_address=192.168.192.40/
static routers=
static domain_name_servers=1.1.1.1
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
denyinterfaces wlan0myshake@raspberryshake:/opt $ interface eth0
-bash: interface: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.192/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.192/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.192/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.192/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.192/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.40/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ static ip_address=192.168.192.40/
-bash: static: command not found
myshake@raspberryshake:/opt $ static routers=
-bash: static: command not found
myshake@raspberryshake:/opt $ static domain_name_servers=1.1.1.1
-bash: static: command not found
myshake@raspberryshake:/opt $ # A sample configuration for dhcpcd.
myshake@raspberryshake:/opt $ # See dhcpcd.conf(5) for details.
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Allow users of this group to interact with dhcpcd via the control socket.
myshake@raspberryshake:/opt $ #controlgroup wheel
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Inform the DHCP server of our hostname for DDNS.
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Use the hardware address of the interface for the Client ID.
myshake@raspberryshake:/opt $ clientid
-bash: clientid: command not found
myshake@raspberryshake:/opt $ # or
myshake@raspberryshake:/opt $ # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
myshake@raspberryshake:/opt $ #duid
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Persist interface configuration when dhcpcd exits.
myshake@raspberryshake:/opt $ persistent
-bash: persistent: command not found
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Rapid commit support.
myshake@raspberryshake:/opt $ # Safe to enable by default because it requires the equivalent option set
myshake@raspberryshake:/opt $ # on the server to actually work.
myshake@raspberryshake:/opt $ option rapid_commit
-bash: option: command not found
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # A list of options to request from the DHCP server.
myshake@raspberryshake:/opt $ option domain_name_servers, domain_name, domain_search, host_name
-bash: option: command not found
myshake@raspberryshake:/opt $ option classless_static_routes
-bash: option: command not found
myshake@raspberryshake:/opt $ # Most distributions have NTP support.
myshake@raspberryshake:/opt $ option ntp_servers
-bash: option: command not found
myshake@raspberryshake:/opt $ # Respect the network MTU.
myshake@raspberryshake:/opt $ # Some interface drivers reset when changing the MTU so disabled by default.
myshake@raspberryshake:/opt $ #option interface_mtu
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # A ServerID is required by RFC2131.
myshake@raspberryshake:/opt $ require dhcp_server_identifier
-bash: require: command not found
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # Generate Stable Private IPv6 Addresses instead of hardware based ones
myshake@raspberryshake:/opt $ slaac private
-bash: slaac: command not found
myshake@raspberryshake:/opt $
myshake@raspberryshake:/opt $ # A hook script is provided to lookup the hostname if not set by the DHCP
myshake@raspberryshake:/opt $ # server, but it should not be run by default.
myshake@raspberryshake:/opt $ #nohook loo
myshake@raspberryshake:/opt $ denyinterfaces wlan0myshake@raspberryshake:/opt $
-bash: denyinterfaces: command not found
myshake@raspberryshake:/opt $
c
cat /etc/resolv.conf
Generated by resolvconf
nameserver 1.1.1.1
Regards David
1 Like
Hello david_s,
Thank you for the complete printout of the two commands. I thought that we were in this situation.
What you see (the many static lines) is the result of a bug that will be fixed in the next Shake OS release and that we are actively working on. To solve your problem, please do the following:
Please open again the dhcpcd.conf file with
sudo nano /etc/dhcpcd.conf
Delete all the lines that start with static, thus leaving only interface eth0. After doing this, paste your latest configuration so that the first section of the file looks like this:
interface eth0
static ip_address=192.168.192.40
static routers=
static domain_name_servers=1.1.1.1
...rest of the file
Filling in the static routers field with the IP address of your router. Then save the file with the sequence Ctrl+X, Y, Enter. Now restart the service with :
sudo service dhcpcd restart
to make sure those changes took hold and then check the output file with
nano /etc/resolv.conf
Your Shake should now display a Static IP address (the one you set) and be able to connect to the internet.
If it doesn’t, please reboot it, then wait ~30 minutes and: 1) download the new logs, 2) print out again the dhcpcd.conf and resolv.conf files, sending all here to me.
Thank you very much for your collaboration.
1 Like
I may have caused some issues when I originally started up. I originally used 192.168.192.40 then realized my router is set only for addresses above 192.168.192.100 so I changed to 192.168.192.192.
I have followed your instructions and my raspberry shake has now found the network.
nano /etc/resolv.conf now gives
nameserver 1.1.1.1
nameserver 8.8.4.4
nameserver 180.76.76.76
Thank you for your help, I believe all is now well. Regards David.S
1 Like
Hello David,
Yes, I can now see your Shake on StationView streaming live data with no issues on both channels.
Happy to have been of help!
Just to say Thank you.
1 Like