The Master isn't accepting ssh connections on the main vlan, but the non-master is. or at least probably would, except I can't connect to it, because I have blacklisted the broken old ssh-rsa host key algorithm So not only is that port probably accessible on the interface I don't want it to be accessible on, but it is likely protected by severely outdated and broken encryption...
ssh-rsa key exchange isn't broken - it's deprecated because it can use a sha1 hash. And sha1 hashes can, at significant expense and time, be chosen-prefix collision attacked.
So in a theoretical future when the sha1 collision can be generated in a few seconds or minutes, a man-in-the-middle attacker on your network could hijack your session.
If you're still running that firmware in 2030-something, with an attacker already inside your network, then you will have to avoid using the SSH functionality.
But already there's not much reason to SSH in to your Unleashed AP.
Almost everything useful is moved already to the web UI. Otherwise I provide a python API to configure Unleashed without using SSH. I already rewrote the home assistant integration to use this, a long time ago.
edit:
If you
must use SSH, and your chosen client OS doesn't let you downgrade SSH security anymore (currently, only non-trusted users on recent centos/rhel/fedora derived distros would have this issue), then
I have a patch which replaces the RSA key with an ECDSA key. Unfortunately, applying the patch will require you to temporarily downgrade your AP firmware, which is a rigmarole, so it's only worth doing if you regularly need SSH access to Unleashed.