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

Set WG ports as part of the client state #675

Closed
AbdelrahmanElawady opened this issue Jan 28, 2024 · 1 comment
Closed

Set WG ports as part of the client state #675

AbdelrahmanElawady opened this issue Jan 28, 2024 · 1 comment
Assignees
Labels
grid-client belongs to grid client type_bug Something isn't working

Comments

@AbdelrahmanElawady
Copy link
Collaborator

Description

When deploying a batch of networks some networks assign the same WG port because they query the node for free ports, assign a random one and then wait until all networks do the same thing. Since it is not recorded anywhere which ports are used before deploying, sometimes multiple networks use the same ports.

@AbdelrahmanElawady AbdelrahmanElawady added type_bug Something isn't working grid-client belongs to grid client labels Jan 28, 2024
@AbdelrahmanElawady AbdelrahmanElawady moved this to In Verification in 3.13.x Jan 29, 2024
@AbdelrahmanElawady AbdelrahmanElawady added this to the 1.0.0 milestone Jan 29, 2024
@AbdelrahmanElawady AbdelrahmanElawady self-assigned this Jan 30, 2024
@Eslam-Nawara
Copy link
Contributor

Verified:
tried deploying batch of 20 networks all with wg access and now all networks get deployed with different wg ports
image

@Eslam-Nawara Eslam-Nawara moved this from In Verification to Done in 3.13.x Mar 4, 2024
@rawdaGastan rawdaGastan modified the milestones: 1.0.0, v0.13.x - v0.14.x Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
grid-client belongs to grid client type_bug Something isn't working
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants