Comment 6 for bug 1935959

thanks yatai, you are right, your patch https://review.opendev.org/c/openstack/neutron/+/833620 can solve the issue. But there is a problem with another scenario.

NetA(geneve) 192.168.10.0/24
external NetB(flat) 100.7.50.0/24

VM-B ip is 192.168.10.20 on host HostA

RouterA gateway network is NetB, NetA is internal interface.

Apply for a floating ip 100.7.50.236, configure port forwarding 100.7.50.236:22 -> 192.168.10.20:22

we can in VM-B access VM-B self, through 100.7.50.236:22.

another scenario:

we add an ip 192.168.10.21(not bind vm) to VM-B, and configure port forwarding 100.7.50.237:22 -> 192.168.10.21:22
we can access 100.7.50.237:22 in external network, but can't in VM-B access self.