One shake connected to network; one shake connected directly by ethernet

Hello,
I have two shakes (both are RS3D): one shake is currently connected to the network and serving data online (we’ll call this the “online shake”). I am also trying to plug in another shake (which we’ll call the “offline shake”) via ethernet to my computer and access the data directly that way without it being online. I have been able to connect to the offline shake no problem previous to me connecting the online shake to the network, and I can connect to my offline shake when I disconnect my computer from the internet. However, when I am connected to the internet, the online shake is the only one I can connect to (both at rs.local and through ssh).

The offline shake does not appear at rs-2.local (or any variation thereof). I was also hoping with the new dashboard would show the IP address of any additional shakes, but when I go there, it only shows the online shake.

I am on a work network and that sometimes throws things off (it also makes it hard to just connect a shake to the network…IT had to allow the other shake to connect), but I was having similar issues on my home network too.

For now, my workaround is just to disconnect my computer from the internet whenever I need to access the offline shake, but any thoughts about how to streamline this?

Hello rbalik, and welcome back to the community!

Given the overall situation, I would recommend checking with the IT department to allow this second Shake too.

However, you mention the fact that the same issue presents itself at home. Does it happen in the exact same way? Or are there differences?

Can you try the following at home, with the “offline” shake?

  • turn off your Shake
  • disconnect all cables from it
  • restart your router (if possible) and wait for it to regain internet connection
  • now reconnect LAN and power cable to the Shake in this order
  • turn on the Shake again

Then wait about an hour, and if you manage to connect in any way, download the logs and send them to me. Let’s see if we can investigate a bit deeper.

Thank you.

Thank you for your reply! I will see if I can do this.

The similar issue I am having at home is the additional shakes not showing up at rs-2.local, but I have not tried that since the new dashboard has been implemented, so I will give it another shot when I have the equipment at home next, and follow your instructions if there are still issues.

Thank you!

1 Like

Hello rbalik, just checking in to see how things are going.

A couple of further details from our software team: the first regards rs.local/. For it to work with the -2, -3, and more suffixes, all Shakes have to share the same subnet. Otherwise, you will only see the Shake that is on the same network as the PC you are trying to access it from.

What you can do is fetch the IP address of the Shake connected via PC, and then access the Shake dashboard using that address in your browser bar, instead of rs.local/.