>
> I pinged 172.17.0.50 from the logical port sw0p1 which has IP
> 11.0.0.3. Since there is a dnat_and_snat entry for this IP, the
> logical flow in table 23 (shown above) is hit and it corrupts xxreg0
> due to the action reg1 = 172.16.1.110.
>
> In table 24, the priority 200 flow is never matched because xxreg0 is
> no longer 3001::b (since it is now 3001:0:ac10:16e::b) and the
> priority 100 flow is hit with the action=(nd_ns { nd.target = xxreg0;
> output; }; output;)
>
> And that's why the IPv6 Neigh Solicitation packet has the wrong nd.target.
>
> I'm afraid your approach doesn't work when a router has NAT entries
> configured. We need to find an alternate solution to address your use
> case.
>
> Thanks
> Numan
>
Thanks a lot for that detailed information.
I'll try to rework it.
Thanks
Felix
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
