loving your distro since decades. Currently transitioning from core to scale.
With this i need to move workloads (VMs, Containers) to the new installation.
Using a bridge to tie together different phsical nics. On this i bound an ip for the truenas services and another for the workloads.
As one of my workloads is (ssh enabled) git, i want to use port 22 on the second ip for gitea.
Unfortunately i can only bind SSH to an interface instead of an ip.
In thread “not-accepted-add-bind-ip-addresses-option-to-ssh-service” (sorry am not allowed to paste links) the option “Auxiliary Parameters” were proposed. Unfortunately the service seems to already inject the required “ListenAddress 1.2.3.4” directive. Can you please reevaluate the original request,@ABain?
Thanks for reaching out. I understand the ask and will do a further review, but we are unlikely to meet this need through aux params. If you have a proposal as an open source project you are free to provide a PR for our engineering team to review.
From my experience in professional and private IT operations, I see this:
A software solution, that tries to offer a converged solution for storage and workloads shall offer an adequate way to bind their services to granular definable resources (ip in that case).
@ABain aw the lack of chance to bind to ip for at least one other truenas builtin service. Think it was SMB and possibly NFS.
Maybe you can evaluate a overarching strategy for services, @ABain .
For SSH the aux parameter would (if working) be only an interim/hack way of addressing this real need.
