Docs are work in progress
Skip to main content

Connecting via SSH

Follow the quick instructions below to connect to your Comet-M via SSH.

  • Ensure your Comet-M device is connected to your local network via Wireless or Ethernet.
  • The default hostname for the Comet-M device is mecha-comet-m.local

MacOS / Linux / Windows​

  • Launch the default Terminal application for your operating system.
$ ssh [email protected]

PuTTY on Windows​

  • Connecting via SSH using PuTTY on Windows
  • When prompted for the password, you can enter mecha as the default password
info

You will be prompted to set a new password on your first connection to SSH, set a stronger password for better security.

That's it, you are now connected to SSH! 🎉

Troubleshooting​

Connection taking too long or timed out?​

  • If the SSH connection takes too long or times out when locating the host, it may be failing hostname resolution. In this case, you may need to locate your device's IP address.
  • First, check if you can ping your Comet-M on its default hostname:
$ ping mecha-comet-m.local
  • The output includes information about your IP Address:
PING mecha-comet-m.local (192.168.29.101): 56 data bytes
64 bytes from 192.168.29.101: icmp_seq=0 ttl=64 time=3.839 ms
64 bytes from 192.168.29.101: icmp_seq=1 ttl=64 time=41.731 ms
  • This implies 192.168.29.101 is your IP address. Try to connect directly via the IP address:
$ ssh [email protected]
  • If you are NOT able to ping the device and the ping timed out, you will need to locate the IP address using the Terminal App on the Homescreen or use the Serial Console.
  • On the Terminal App or Serial Console, run the following command to locate the IP Address:
  • If you are connected via Wireless:
$ ifconfig | grep -A 5 wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 10.211.55.12  netmask 255.255.255.0  broadcast 10.211.55.255
inet6 fdb2:2c26:f4e4:0:2060:514b:6cc7:26e7  prefixlen 64  scopeid 0x0<global>
inet6 fdb2:2c26:f4e4:0:9aeb:e8d9:4619:abc3  prefixlen 64  scopeid 0x0<global>
inet6 fe80::b971:ee23:27d0:833  prefixlen 64  scopeid 0x20<link>
ether 00:1c:42:e1:26:ac  txqueuelen 1000  (Ethernet)
  • If you are connected via Ethernet:
$ ifconfig | grep -A 5 eth0
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 10.211.55.12  netmask 255.255.255.0  broadcast 10.211.55.255
inet6 fdb2:2c26:f4e4:0:2060:514b:6cc7:26e7  prefixlen 64  scopeid 0x0<global>
inet6 fdb2:2c26:f4e4:0:9aeb:e8d9:4619:abc3  prefixlen 64  scopeid 0x0<global>
inet6 fe80::b971:ee23:27d0:833  prefixlen 64  scopeid 0x20<link>
ether 00:1c:42:e1:26:ac  txqueuelen 1000  (Ethernet)
  • The IP address of your Comet-M is highlighted in the output.
  • If there is no IP address displayed, you will need to check the network connectivity for your Comet-M.

Debugging SSH connection​

  • To find out more on why the SSH connection failed, you can use the below command to debug further:
$ ssh -vvv [email protected]
  • Review the logs for more information on why the connection failed.

Device Specifications​

[The rest of the device specifications remain the same as in the previous version]