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

Add listing of all nat entries to gRPC protocol #638

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

PlagueCZ
Copy link
Contributor

Added the option to list all NAT entries by providing address 0.0.0.0 as the filter (the client does that automatically if no filter is given).

During implementation I also noticed a bug that is closely connected, so I included it here. Also there was an obsolete log line for listing the neighboring nats.

Fixes #637

The change required changing the protobuf specification, but I only added a field at the end, which should ensure backwards-compatibility and also enable old client code to use dpservice-go library without any issues.
That is why the names in the gRPC structure are looking strange.

This code is running on one node in OSC LAB, with an old metalnet, so backwards compatibility is tested.

Removed nat-ip from required flags of list nats  and it now defaults to 0.0.0.0
@github-actions github-actions bot added enhancement New feature or request size/L labels Jan 17, 2025
@PlagueCZ PlagueCZ requested a review from guvenc January 17, 2025 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add the ability to list all nat entries without the knowledge of NAT IP
1 participant