Skip to content

Conversation

@PlagueCZ
Copy link
Contributor

This is a proposal for renaming some neighnat-only functions.

Fixes #692

@PlagueCZ PlagueCZ requested a review from a team as a code owner June 24, 2025 16:25
@github-actions github-actions bot added size/M enhancement New feature or request labels Jun 24, 2025
@guvenc guvenc modified the milestone: H1/2025 Jun 25, 2025
@guvenc
Copy link
Collaborator

guvenc commented Jun 25, 2025

@PlagueCZ
Would you please rebase ?

@PlagueCZ PlagueCZ force-pushed the feature/rename_neighnat_functions branch from 0aaf95d to 948e235 Compare June 25, 2025 10:23
Copy link
Contributor

@byteocean byteocean left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks.

@guvenc guvenc merged commit 948e235 into main Jun 25, 2025
6 checks passed
@guvenc guvenc deleted the feature/rename_neighnat_functions branch June 25, 2025 11:22
@github-project-automation github-project-automation bot moved this to Done in Roadmap Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Neighnat-only functions names seem to work with all NAT entries

5 participants