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

Implement checking that listen sockets from Tempesta FW configuration is not used #2050

Open
EvgeniiMekhanik opened this issue Feb 1, 2024 · 1 comment
Labels
good to start Start form this tasks if you're new in Tempesta FW scripts tempesta.sh and other scripts
Milestone

Comments

@EvgeniiMekhanik
Copy link
Contributor

EvgeniiMekhanik commented Feb 1, 2024

Motivation

Currently if administrator chooses in the configuration the listen addresses that are already in use by other process, Tempesta FW fail to start. Moreover if Tempesta is already work it will be stopped. For better usability it will be good to check that sockets from configuration is not already used by other process.

What should be done

There are a lot of ways to specify listen address in Tempesta config, so the best way to solve this task is to write small python script, which will use regular expressions to parse Tempesta config and check if this addresses are in use. This script should be called from tempesta.sh and if returns error, Tempesta loading should be cancelled.

@EvgeniiMekhanik EvgeniiMekhanik added the good to start Start form this tasks if you're new in Tempesta FW label Feb 1, 2024
@EvgeniiMekhanik EvgeniiMekhanik added this to the 1.1: TBD milestone Feb 1, 2024
@EvgeniiMekhanik EvgeniiMekhanik added the scripts tempesta.sh and other scripts label Feb 1, 2024
@krizhanovsky
Copy link
Contributor

This task is separated from #2017 and #2043 addressed in pull request #2045

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good to start Start form this tasks if you're new in Tempesta FW scripts tempesta.sh and other scripts
Projects
None yet
Development

No branches or pull requests

2 participants