This bug is verified on the latest version.The traffic is all though the external port, not through the geneve port: [root@dell-per730-19 ~]# uname -a Linux dell-per730-19.rhts.eng.pek2.redhat.com 3.10.0-957.el7.x86_64 #1 SMP Thu Oct 4 20:48:51 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [root@dell-per730-19 ~]# rpm -qa | grep openvswitch kernel-kernel-networking-openvswitch-ovs_qinq-1.3-34.noarch openvswitch2.11-2.11.0-9.el7fdp.x86_64 kernel-kernel-networking-openvswitch-ovn-1.0-121.noarch openvswitch-selinux-extra-policy-1.0-11.el7fdp.noarch [root@dell-per730-19 ~]# rpm -qa | grep ovn kernel-kernel-networking-openvswitch-ovn-1.0-121.noarch ovn2.11-2.11.0-16.el7fdp.x86_64 ovn2.11-host-2.11.0-16.el7fdp.x86_64 ovn2.11-central-2.11.0-16.el7fdp.x86_64 [root@dell-per730-19 ~]# root@dell-per730-57 ovn]# ovn-nbctl lsp-get-options s2_r1 nat-addresses=router router-port=r1_s2 [root@dell-per730-57 ovn]# ovn-nbctl lsp-get-addresses s2_r1 router [root@dell-per730-57 ovn]# ovn-nbctl get Logical_Router_Port r1_s2 options:redirect-chassis "hv1" [root@dell-per730-57 ovn]# [root@dell-per730-57 ovn]# ovn-nbctl show switch d731ce3c-8725-4550-9767-2c4a88e3779d (s3) port s3_r1 type: router addresses: ["00:de:ad:ff:01:03 172.16.103.1"] router-port: r1_s3 port ln-s3 type: localnet addresses: ["unknown"] port hv0_vm01_vnet1 addresses: ["00:de:ad:00:01:01 172.16.103.12"] port hv0_vm00_vnet1 addresses: ["00:de:ad:00:00:01 172.16.103.11"] switch 4b179a53-cfdd-497c-bd09-007b5a3cfd77 (s2) port ln-s2 type: localnet addresses: ["unknown"] port hv1_vm01_vnet1 addresses: ["00:de:ad:01:01:01 172.16.102.12"] port s2_r1 type: router router-port: r1_s2 port hv1_vm00_vnet1 addresses: ["00:de:ad:01:00:01 172.16.102.11"] router c73c4df6-0308-4b0b-8c1c-4bbe3581b96c (r1) port r1_s3 mac: "00:de:ad:ff:01:03" networks: ["172.16.103.1/24"] port r1_s2 mac: "00:de:ad:ff:01:02" networks: ["172.16.102.1/24"] nat 6fa543bf-ebbb-4e0e-a3fa-630c8af55d11 external ip: "172.16.102.200" logical ip: "172.16.103.11" type: "dnat_and_snat" [root@dell-per730-57 ovn]# [root@dell-per730-57 ovn]# ovn-nbctl lr-nat-list r1 TYPE EXTERNAL_IP LOGICAL_IP EXTERNAL_MAC LOGICAL_PORT dnat_and_snat 172.16.102.200 172.16.103.11 00:de:ad:00:00:01 hv0_vm00_vnet1 [root@dell-per730-57 ovn]# rtt min/avg/max/mdev = 0.215/0.310/1.111/0.071 ms [root@localhost ~]# ping 172.16.102.200 PING 172.16.102.200 (172.16.102.200) 56(84) bytes of data. 64 bytes from 172.16.102.200: icmp_seq=1 ttl=63 time=1.12 ms 64 bytes from 172.16.102.200: icmp_seq=2 ttl=63 time=0.301 ms 64 bytes from 172.16.102.200: icmp_seq=3 ttl=63 time=0.289 ms 64 bytes from 172.16.102.200: icmp_seq=4 ttl=63 time=0.328 ms 64 bytes from 172.16.102.200: icmp_seq=5 ttl=63 time=0.298 ms 64 bytes from 172.16.102.200: icmp_seq=6 ttl=63 time=0.287 ms captured on the peer machine: [root@dell-per730-19 ~]# tcpdump -ei p4p2 -nn | grep ICMP tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on p4p2, link-type EN10MB (Ethernet), capture size 262144 bytes 07:22:23.019243 00:de:ad:01:00:01 > 00:de:ad:00:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.11 > 172.16.102.200: ICMP echo request, id 6903, seq 9, length 64 07:22:23.019473 00:de:ad:00:00:01 > 00:de:ad:01:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.200 > 172.16.102.11: ICMP echo reply, id 6903, seq 9, length 64 07:22:24.019263 00:de:ad:01:00:01 > 00:de:ad:00:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.11 > 172.16.102.200: ICMP echo request, id 6903, seq 10, length 64 07:22:24.019480 00:de:ad:00:00:01 > 00:de:ad:01:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.200 > 172.16.102.11: ICMP echo reply, id 6903, seq 10, length 64 07:22:25.019254 00:de:ad:01:00:01 > 00:de:ad:00:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.11 > 172.16.102.200: ICMP echo request, id 6903, seq 11, length 64 07:22:25.019472 00:de:ad:00:00:01 > 00:de:ad:01:00:01, ethertype IPv4 (0x0800), length 98: 172.16.102.200 > 172.16.102.11: ICMP echo reply, id 6903, seq 11, length 64 ^C88 packets captured 88 packets received by filter 0 packets dropped by kernel
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:1385