bpf, nat46x64: move RFC6052 prefix into node config - #43799
Merged
Conversation
viktor-kurchenko
added
area/loader
42 tasks
Contributor
Author
|
/test |
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
January 16, 2026 07:11
b73ca7b to
1158395
Compare
Contributor
Author
|
/ci-verifier |
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
January 16, 2026 08:03
1158395 to
c8d00e7
Compare
Contributor
Author
|
/ci-verifier |
Contributor
Author
|
/test |
viktor-kurchenko
marked this pull request as ready for review
January 16, 2026 08:32
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
January 16, 2026 08:34
c8d00e7 to
b18f80b
Compare
Contributor
Author
|
/test |
jrife
previously requested changes
Jan 22, 2026
ti-mo
requested changes
Jan 28, 2026
ti-mo
left a comment
ti-mo
left a comment
Contributor
There was a problem hiding this comment.
As Jordan pointed out, let's use v4addr for this fields, that's what they're for! 😉 I'm working on making dpgen output Go types for C structs as well, but it's not quite ready.
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
2 times, most recently
from
February 4, 2026 15:09
c4269ee to
10c62de
Compare
Contributor
Author
|
/test |
ti-mo
approved these changes
Feb 5, 2026
ti-mo
approved these changes
Feb 5, 2026
Contributor
|
@viktor-kurchenko Sorry, looks like this needs a rebase. |
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
February 5, 2026 11:18
10c62de to
e571c29
Compare
Contributor
Author
|
/test |
ti-mo
enabled auto-merge
February 5, 2026 12:02
rgo3
approved these changes
Feb 5, 2026
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
February 6, 2026 18:03
e571c29 to
4645155
Compare
Contributor
Author
|
Rebased to resolve conflicts. |
Contributor
Author
|
/test |
borkmann
approved these changes
Feb 9, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Feb 9, 2026
This commit moves NAT 46x64 RFC6052 prefix bytes into the node configuration so BPF programs consume CONFIG(nat_46x64_prefix) value instead of C header defines. The Go datapath now populates this field from the NAT46x64 config, and the headerfile writer no longer emits NAT_46X64_PREFIX_ defines. Updates included: - BPF nat_46x64 helpers switched to CONFIG(nat_46x64_prefix). - Node config population moved to runtime config and legacy defines dropped. Signed-off-by: viktor-kurchenko <[email protected]>
viktor-kurchenko
force-pushed
the
pr/vk/bpf/nat/cfg
branch
from
February 10, 2026 11:19
4645155 to
91b6515
Compare
Contributor
Author
|
Rebased to resolve conflicts. |
Contributor
Author
|
/test |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit moves NAT 46x64 RFC6052 prefix bytes into the node configuration so BPF programs consume CONFIG(nat_46x64_prefix) values instead of C header defines.
The Go datapath now populates these fields from the NAT46x64 config, and the headerfile writer no longer emits NAT_46X64_PREFIX_ defines.
Updates included: