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 nat46 in-kernel translator support #36

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

oskar456
Copy link
Contributor

@oskar456 oskar456 commented Nov 5, 2023

This allows clatd to use nat46 kernel translator instead of TAYGA. It uses automatic detection - if nat46 module is loaded, it will get used, otherwise the application falls back to using TAYGA.

This has been developed during IETF 118 hackathon.

This allows clatd to use [nat46](https://github.com/ayourtch/nat46)
kernel translator instead of TAYGA. It uses automatic detection - if
`nat46` module is loaded, it will get used, otherwise the application
falls back to using TAYGA.

Signed-off-by: Ondřej Caletka <[email protected]>
@toreanderson
Copy link
Owner

Cool! I assume you've tested that it works fine, both using the kernel module and TAYGA?

@oskar456
Copy link
Contributor Author

oskar456 commented Nov 6, 2023

Yes, it is tested and it works for me both with and without the kernel module loaded. The kernel module is preferred if available - there is no config option to deprefer it. I think this is not an issue as you probably won't have the module loaded unless you want to use it for clat.

@toreanderson toreanderson merged commit 04062b2 into toreanderson:master Nov 7, 2023
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