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

IPv6 Overlay Support for offloading path #467

Open
guvenc opened this issue Jan 10, 2024 · 2 comments
Open

IPv6 Overlay Support for offloading path #467

guvenc opened this issue Jan 10, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@guvenc
Copy link
Collaborator

guvenc commented Jan 10, 2024

Summary

Support the offloading of the following IPv6 networking functions which already work in the non-offloading path.

  • VM to VM communication on same Hypervisor.
  • VM to VM communication different Hypervisor.
  • LB
  • NAT64
@guvenc guvenc added the enhancement New feature or request label Jan 10, 2024
@guvenc guvenc moved this to In Progress in Networking Jan 10, 2024
@byteocean
Copy link
Contributor

NAT64 remains to be investigated.

@byteocean byteocean moved this from In Progress to OnHold in Networking Jul 24, 2024
@byteocean
Copy link
Contributor

NAT64 can be implemented using newly supported RTE_FLOW_ACTION_TYPE_NAT64 in DPDK 24.03. The experiments show that in general it could work, but cannot be integrated into dpservice yet due to the following reasons:

  1. IPinIP tunnel matching is not yet supported by the mlx5 driver;
  2. NAT64 action in DPDK 24.03 is designed to bridge IPv4 and IPv6 world by converting both src/dst IP addresses, which has slight difference compared to the NAT64 concept in dpservice. Thus, the complex combination, decap/encap/nat64/modify_field/port, is needed but still has flaws.

Point 1 is known issue, point 2 needs to further communicate via mailing-list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: OnHold
Development

No branches or pull requests

2 participants