Egress on dual-stack testbed

[Atish-iaf]

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

1. Create a dual-stack kind cluster.
2. Create a Pod, apply Egresses(static EgressIP IPv4/IPv6) on that Pod.
3. 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]

@tnqn

[github-actions[bot]]

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]]

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]]

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]]

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