[ovs-git] [ovn-org/ovn] ff3e11: ovn-northd: Add ARP responder flows for SNAT entries.

numansiddique noreply at github.com
Tue Aug 11 15:37:54 UTC 2020


  Branch: refs/heads/branch-20.06
  Home:   https://github.com/ovn-org/ovn
  Commit: ff3e1172959e9e88076e2b597e1d50b6bc7af239
      https://github.com/ovn-org/ovn/commit/ff3e1172959e9e88076e2b597e1d50b6bc7af239
  Author: Numan Siddique <numans at ovn.org>
  Date:   2020-08-11 (Tue, 11 Aug 2020)

  Changed paths:
    M northd/ovn-northd.8.xml
    M northd/ovn-northd.c
    M tests/ovn-northd.at
    M tests/system-ovn.at

  Log Message:
  -----------
  ovn-northd: Add ARP responder flows for SNAT entries.

If the below SNAT entry is added:
ovn-nbctl lr-nat-add snat 172.168.0.120 10.0.0.5

And when the logical port with IP - 10.0.0.5, sends a packet destined to
outside, gets SNATted to 172.168.0.120 as expected, but for the reverse traffic
if the upstream switch sends an ARP request for 172.168.0.120, then OVN doesn't
reply and the reply traffic never reaches the logical port.

This patch fixes this issue by addding ARP responder flows for SNAT entries.

Note that, if 172.168.0.120 happens to be the logical router IP, then it works.

Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=1861294
Reported-by: Alexander Constantinescu <aconstan at redhat.com>
Acked-by: Dumitru Ceara <dceara at redhat.com>
Signed-off-by: Numan Siddique <numans at ovn.org>

(cherry-picked from master commit e2aa124ff7c24e3128951fce13ca24337121ad27)




More information about the git mailing list