Allow SSH to be bound to specific IPs as opposed to just interfaces

[dull.wire]

Allow SSH to be bound to specific IPs as opposed to interfaces.

Currently the SSH service can only be bound to an interface, which in turn means port 22 is reserved on all IP aliases on this interface.

If implemented, port 22 can be used on other IP aliases are bound to Apps that provide an ssh endpoint (for example GitLab or Forgejo).

Problem/Justification

Allow SSH to be bound to specific IPs as opposed to interfaces. Currently the SSH service can only be bound to an interface, which in turn means port 22 is reserved on all IP aliases on this interface. If implemented, port 22 can be used on other IP aliases are bound to Apps that provide an ssh endpoint (for example GitLab or Forgejo).

[Stux]

I think this is a duplicate of:

Add "Bind IP Addresses" option to SSH Service

Problem/Justification SSH Service (sshd) can only currently be confiugured to bind to a specific interfaces. This means that the sshd instance will bind to all IP Aliases/Addresses configured on that interface. Thus there is no way to vacate port 22 on an IP Alias, which means the IP Alias can not be used for binding port 22 in an app or docker-compose. This is the current adanced settings for ssh service [Screenshot 2024-09-02 at 12.38.42 PM] This is the bind IP address UI from SMB servi…