Skip to content

Commit 3a1761c

Browse files
committed
add MacOS mDNS troubleshooting
1 parent dd876d0 commit 3a1761c

File tree

1 file changed

+17
-0
lines changed
  • content/hardware/02.uno/boards/uno-q/tutorials/05.ssh

1 file changed

+17
-0
lines changed

content/hardware/02.uno/boards/uno-q/tutorials/05.ssh/ssh.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,7 @@ Which means it is working properly. ✅
5252

5353
***If you are running an outdated/custom system that for some reason does not feature SSH, you can look into installing [OpenSSH](https://formulae.brew.sh/formula/openssh) and [LibreSSL](https://formulae.brew.sh/formula/libressl) manually via, e.g., Brew.***
5454

55+
5556
### Windows
5657

5758
Later versions of Windows (10+) include SSH clients as well, with no requirement to install additional tools. To verify tools are installed, open a terminal on your Windows machine, and type:
@@ -110,6 +111,22 @@ See below how it should look when you have successfully accessed the board's she
110111

111112
![macOS SSH access](assets/ssh-macos.png)
112113

114+
#### MacOS MDNS Issues
115+
116+
If the connection fails with the following error:
117+
- `ssh: connect to host <boardname>.local port 22: Connection refused`
118+
119+
It might be a mDNS issue with your local network. To work around this, there are some alternatives to try:
120+
121+
**Connect directly via the IP address:** The board's IP address can be found through:
122+
- Arduino IDE 2 (needs the Zephyr core installed)
123+
- Arduino CLI, by running `arduino-cli board list`
124+
- Running `hostname -I` while in the board's shell. You can access the board via `adb shell` ([instructions](/software/app-lab/tutorials/cli/#connect-via-adb)), or [using the board in SBC mode](/tutorials/uno-q/single-board-computer/).
125+
126+
After obtaining the IP address, you should be able to connect via SSH using `ssh arduino@10.0.20.138`.
127+
128+
***If you have previously connected to a board with the same IP address, but have re-flashed the board, you may need to remove the old key from `~/.ssh/known_hosts`. This can be done by editing the `known_hosts` file or by running `ssh-keygen -R <board ip address>`.***
129+
113130
### Windows Confirmation
114131

115132
![Windows SSH access](assets/ssh-windows.png)

0 commit comments

Comments
 (0)