GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.

user interface for advanced scenarios

The protocol support is in dnsjit, but there needs to be some shotgun interface how to configure them.

Some example test cases that should be possible to configure:

100 % UDP
100 % TCP with 10s idle timeout
100 % TLS, customize priority
80 % TCP with 10s idle timeout, 20 % TCP with no idle timeout
80 % UDP, 10 % TLS with session resumption, 10 % TLS without session resumption

The interface should:

separate test-case from the machine-specific parameters (such as number of threads, IPs)
take care of mapping the test-case to individual threads and IPs - make the test case portable to different machine
be easily read/write-able by humans
be extendable and future-proof (e.g. allow different future protocols and their specific configuration)

Edited Sep 14, 2020 by Tomas Krizek