Unable to Connect via SSH on Armbian 22.11.2

[uninvitedguest]

After setting up the board through the serial terminal, I am unable to connect to the board using ssh. I receive the error

<ipaddress> port 22: No route to host.

This happens on both Jammy & Bullseye. I can confirm that the board is connected to wifi/internet (using Radxa A8 module). I’ve attempted to reinstall the SSH server which hasn’t resolved the issue.

Any help is appreciated. Thanks!

[igorp]

Perhaps try this way: https://www.armbian.com/bugs/

[chapas]

Hi,
did you try to enable it in ‘armbian-config’?

[uninvitedguest]

I had, that didn’t affect anything.

I solved the issue by setting a static IP within armbian-config. Previously I had set the static IP using my router’s DHCP server, and even though the board would output the IP I had set any attempts to SSH in to it would fail. After setting the static IP using the router and in armbian-config, the issue seems to have resolved.

[uninvitedguest]

Looks like the issue with remote sessions continues to persist in a new way - while ssh and other direct connections (IP:Port for services like Nextcloud, etc) work for a bit after a recent reboot, after some unknown amount of uptime the board stops accepting any new remote connections through SSH/etc.

Will post to the armbian forum.

[incognito]

The thing seems to be that armbian is confused by the network interfaces.
There are 2 interfaces on Radxa WiFi A8:
wlP2p33s0 and wlan1. When I log in to Ubuntu, it seems to be selecting wlan1 and before that or in Gnome it is the other one. This causes some network weirdness. How to force armbian not to use the ubuntu network manager?

[Ivars_Vids]

I had same issue.You need to generate Host key and restart sshd service.

to generate host key type ssh-keygen -A

[incognito]

Ok, I was wrong. wlP2p33s0 is preferred every time, but ssh server works only before logging in to Ubuntu. Generating a new host key and restarting the sshd service did not change anything.
Setting a static IP also did not change anything. The ssh server works just until the first login.

[uninvitedguest]

As a fun new quirk, after having my board offline for a number of days, I’ve booted it up and the device mac address has changed - resulting in the DHCP server on my router assigning it a random IP address, even though armbian-config had been set to static as well.

[nobrowser]

@uninvitedguest has this ever been resolved? I know if ssh is not reliable I do not want this board …

[incognito]

It is resolved. Here is the solution.

Radxa A8 WiFi Device Names

There is some confusion about the multiple device names when using the Radxa A8 WiFi module. By default, one of the names is assigned a udev name like wlP2p33s0, the other uses fallback naming logic and is assigned a kernel name of wlan0 or wlan1. Indeed, in order to make your connections work you need to specify the device (using Network Manager, etc). The problem I see, however, is these device names are not consistently being assigned. The device that gets the udev name on one boot could …

[nobrowser]

I see, thank you.

–
Ian