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.

Sign up for GitHub

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

Jump to bottom

Egress on dual-stack testbed #4532

Open

Atish-iaf opened this issue Jan 4, 2023 · 6 comments

Assignees

Labels

area/transit/egress kind/bug

Contributor

Atish-iaf commented Jan 4, 2023 •

edited

Loading

Describe the bug

On dual-stack testbed, if Egress having IPv4 EgressIP is applied to a Pod, then it is applicable to only IPv4 packets from that Pod and not to IPv6 packets from that Pod. Similarly if IPv6 EgressIP, then applicable to only IPv6 packets from that Pod.

On applying two Egresses on a Pod, first Egress with IPv4 EgressIP and second Egress with IPv6 EgressIP, only first Egress with IPv4 EgressIP is applied to IPv4 packets from that Pod and second Egress with IPv6 EgressIP is not applied to IPv6 packets from that Pod. No Egress is applied to IPv6 packets from that Pod. Similar result for first Egress with IPv6 EgressIP and second Egress with IPv4 EgressIP. Actually only first Egress is applied packets(IPv4 packet if first EgressIP is IPv4) from that Pod .

To Reproduce

Create a dual-stack kind cluster.
Create a Pod, apply Egresses(static EgressIP IPv4/IPv6) on that Pod.
Do traceflow with source as the above Pod, and destination as any external IPv4/IPv6 for IPv4 and IPv6 packet respectively.

Expected

Actual behavior

Versions:

Additional context

Atish-iaf added the kind/bug label

Contributor Author

Atish-iaf commented Jan 4, 2023

Atish-iaf added the area/transit/egress label

Contributor

github-actions bot commented Apr 23, 2023

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions bot added the lifecycle/stale label

Atish-iaf removed the lifecycle/stale label

Contributor

github-actions bot commented Oct 17, 2023

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions bot added the lifecycle/stale label

Atish-iaf removed the lifecycle/stale label

Contributor

github-actions bot commented Jan 21, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions bot added the lifecycle/stale label

rajnkamr assigned KMAnju-2021

github-actions bot removed the lifecycle/stale label

Contributor

github-actions bot commented May 3, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions bot added the lifecycle/stale label

Atish-iaf removed the lifecycle/stale label

Contributor

github-actions bot commented Aug 14, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions bot added the lifecycle/stale label

rajnkamr removed the lifecycle/stale label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment