Hi. Please can you look into the issues with station R4921? I included logs and a screenshot of the issue. Thanks.
RSH.R4921.2024-06-11T12_23_35.logs.tar (3.6 MB)
-What is the problem you are experiencing?
Data seldom appears in Data View (see attached screenshot with only 2 data points in 24 hours). There is no data appearing on Live Streaming.
Firewall is open in all recommended ports and traffic through them is excluded from packet filtering.
-When did it first appear? (Was it after a power cut?)
From the first time the machine connected to the remote server.
-Is your RS connected to a home or school/office network?
Connected to a school network.
-Has your hardware (Shake board, power supply, Raspberry Pi, etc.) been supplied entirely by us?
Yes
1 Like
Hello Dunelmshake, and welcome to the community!
Thank you for the detailed explanation, the screenshot, and the logs above all. They have been very helpful.
I can see that the Shake boots up and operates optimally, bar the network issue that you have highlighted, of course. There are many trials that ultimately fail, as shown in these lines:
2024 161 11:14:49>> DDSsend(): Send error: 0
2024 161 11:14:49>> sendDClientDP(): Error sending data ...
2024 161 11:20:06>> DDSsendDP(): message send failed after 61 retries, closing connection.
Is it possible that the firewall and/or school router (this has happened in the past with other Shakers) automatically closes the connection when the Shake manages to transmit something? Other users have solved this by adding the Shake IP (and MAC address, if required) to their firewall exceptions.
If you have already covered all this in your school firewall setup, could I then please ask you to log into the Shake (if needed, instructions on how to do so can be found here: Please read before posting!), execute the following two commands:
cat /etc/dhcpcd.confcat /etc/resolv.conf
and post their output here? Thank you!
Hello Stormchaser,
It took a while to gain access to the machine. Please find enclosed the contents of the configuration files you requested:
/etc/dhcpcd.conf
interface eth0
static domain_name_servers=192.168.4.140 192.168.4.141 8.8.8.8
static ip_address=192.168.15.7/23
static routers=192.168.14.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 wlan0
/etc/resolv.conf
#Generated by resolvconf
nameserver 8.8.4.4
nameserver 180.76.76.76
Regards,
Dunelmshake
Hello Dunelmshake,
No problem at all, and thanks for the config files contents that you have attached. dhcpcd.conf and resolv.conf look good from what I can see, so we need to proceed to the next step.
Can you SSH again into the Shake and execute these commands for me?
ping -c 5 8.8.8.8ping -c 5 144.91.66.87nc -zvw5 144.91.66.87 55555nc -zvw5 144.91.66.87 55556
And also:
traceroute 8.8.8.8traceroute 144.91.66.87
And post their output here? Thank you!
