Hello, Your first flow “in_port=4, ip, ….” matches only IP traffic, but ARP is not matched. You need another rule like “in_port, arp, actions….” to translate also ARP.
Cheers, DC > On Jul 7, 2016, at 11:36 AM, Cristina Palomo Regidor > <cristina.palomo.regi...@ericsson.com> wrote: > > Hello, > I would appreciate any help on this nat example. I want to do dst nat > translation so the dst address is translated to 172.16.1.5 where I have a web > server. > > I have implemented these flows: > > ovs-ofctl add-flow br0 > "in_port=4,ip,action=ct(commit,zone=1,nat(dst=172.16.1.5)),5" > ovs-ofctl add-flow br0 > "in_port=5,ct_state=-trk,ip,action=ct(table=0,zone=1,nat)" > ovs-ofctl add-flow br0 "in_port=5,ct_state=+trk,ct_zone=1,ip,action=4" > > Are they correct? > > If I do from my client (port 4) curl 172.16.1.4:80 with the purpose of nat > translating the dst address to the web server address I only see arp requests > of this type in a tcpdump: > 12:17:52.196395 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 172.16.1.4 tell 172.16.1.1, length 28 > 12:17:53.199288 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 172.16.1.4 tell 172.16.1.1, length 28 > > Could you help me on how to make this work? > > Thanks and BR/ > > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org <mailto:discuss@openvswitch.org> > http://openvswitch.org/mailman/listinfo/discuss > <http://openvswitch.org/mailman/listinfo/discuss>
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
