You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently the server port of the floating license server can be specified with -server.port, this is good.
However, there is no option to specify the binding address, instead the "wildcard" 0.0.0.0 is always used, which translates to "use all addresses of this system". This assumes either
that a server has only one network interface and that this network interface has only one address
or
that the server should always listen on all addresses of the system.
Both assumptions are wrong.
A network interface can have multiple addresses. A server can, and usually has, multiple network interfaces.
In most cases the server software (fls) should only listen on one address.
Therefore, I suggest to add a command line parameter to specify the binding address of the server, e.g. -server.bindaddress.
I have prepared a working solution to either provide a binding address, or assume as default to listen on all addresses.
Technically -server.bindadress should be a list of addresses. However, the solution mentioned above covers most use cases and is a starting point.
Best regards
Jens
The text was updated successfully, but these errors were encountered:
Hi there,
currently the server port of the floating license server can be specified with -server.port, this is good.
However, there is no option to specify the binding address, instead the "wildcard" 0.0.0.0 is always used, which translates to "use all addresses of this system". This assumes either
or
Both assumptions are wrong.
A network interface can have multiple addresses. A server can, and usually has, multiple network interfaces.
In most cases the server software (fls) should only listen on one address.
Therefore, I suggest to add a command line parameter to specify the binding address of the server, e.g. -server.bindaddress.
I have prepared a working solution to either provide a binding address, or assume as default to listen on all addresses.
Technically -server.bindadress should be a list of addresses. However, the solution mentioned above covers most use cases and is a starting point.
Best regards
Jens
The text was updated successfully, but these errors were encountered: