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

Rework creation of route tables #435

Closed

Conversation

NikitaSkrynnik
Copy link
Contributor

@@ -54,19 +53,28 @@ func create(ctx context.Context, conn *networkservice.Connection, tableIDs *Map,
return errors.WithStack(err)
}

tableMap, ok := tableMaps.Load(conn.NetworkServiceEndpointName)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a NSC is connected to 2 NSEs, there might be a conflict since the counter will be separated for the 2 connections. A policy for NSE-1 will create a table and rule with table ID 1, and another policy for NSE-2 will select the same table ID.

I suggest to use the NET NS URL as key instead. I have proposed this change in this PR: #433

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 this pull request may close these issues.

2 participants