-
Notifications
You must be signed in to change notification settings - Fork 3.4k
test: Enable IPv6 datapath_configuration tests with BPF masquerading #26500
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
Conversation
892bc97
to
0191017
Compare
/test |
0191017
to
ecb6cbb
Compare
ecb6cbb
to
d7df97d
Compare
/test |
d7df97d
to
7a8b1ae
Compare
/test |
7a8b1ae
to
a5a6dde
Compare
/test |
Fails on bpf-next only, which is the only setup where we have the 3rd node without K8s, necessary condition to run the test. Maybe worth trying to replicate without masquerading, to check whether simple IPv6 connects at all in this configuration (thanks Julian for the suggestion). |
This pull request has been automatically marked as stale because it |
This pull request has not seen any activity since it was marked stale. |
Following the introduction of IPv6 BPF masquerading, we can enable the related tests in datapath_configuration.go. Signed-off-by: Quentin Monnet <qmo@qmon.net>
a5a6dde
to
21e46cb
Compare
/test |
Still not working. No cycles for looking into this, I'm closing the PR. |
Following the introduction of IPv6 BPF masquerading, we can enable the related tests in datapath_configuration.go.
Logically, these tests should have been enabled when we added IPv6 BPF masquerading, but I missed them.