Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FLS cannot define server bind address #1101

Closed
iils-jschmidt opened this issue Jun 28, 2022 · 2 comments · Fixed by #1106
Closed

FLS cannot define server bind address #1101

iils-jschmidt opened this issue Jun 28, 2022 · 2 comments · Fixed by #1106
Assignees

Comments

@iils-jschmidt
Copy link
Contributor

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

  • 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

@eparovyshnaya eparovyshnaya self-assigned this Jun 28, 2022
@iils-jschmidt
Copy link
Contributor Author

PR
#1102

@iils-jschmidt
Copy link
Contributor Author

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants