With a brand new robot, polyscope version 5.24.1 I set up the SSH connection in the settings (on Polyscope) and tried connecting. The robot is in the same subnet, profinet works, the SSH Access is enabled and password based is enabled, the robot can be pinged but the SSH connection always times out. It doesn’t get refused and it doesn’t say unknown host. It just times out.
Nothing I found online or on the forums helped me acchieve a connection. The robot could connect to itself through ssh which made me doubt some of the firewall/network restriction settings.
After a LOT of troubleshooting, adding the line sudo iptables -I INPUT -p tcp --dport 22 -j ACCEPT resolved the issue. Of course, this only works until the first restart, but at least I can do something now.
The VNC suffered from the same issue. After I added the upper command with the corresponding port, it magically started working.
Why do these ports remain blocked for incomming trafic even after the Secure Shell gets enabled from the Polyscope? Is this a known issue? Is there a better solution for it? Am I the only one who is currently suffering from this problem (happend with two robots within 2 months - thought someone missconfigured something on the first one since it was a used demo robot)?
I will gladly provide more information if needed.
