fix(ts3server): improve ts3 ip parsing #2789
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For Teamspeak3-Servers: Only use the first IP specified within the ts3server.ini file. The IP string is cut off after the first appearance of a comma (IP seperator within ts3server.ini files).
Description
As described inte teamspeak server documentation the voice_ip parameter allows a comma separated IP list. Currently when e.g. "voice_ip=12.345.678.910, 1a23:b456:7891:011::1" is specified which is according to ts standards LinuxGSM will extract "12.345.678.910 1a23b45678910111" as IP string and can not deal with it. As a workaround till more then one IP and IPv6 is supported the IP string should be cut off after the first appearance of a comma.
Fixes #2658
Type of change
Checklist
PR will not be merged until all steps are complete.
develop
branch as its base.Documentation
If documentation does need updating either update it by creating a PR (preferred) or request a documentation update.
Thank you for your Pull Request!