Chelsio Communications Terminator 6, Installation And User Manual, Page: 305 / 432

Chapter XXI. OVS Kernel Datapath Offload
Chelsio Unified Wire for Linux 305
•
Exact-match flow to match 4-tuple IPv4 traffic and do NAT rewrite:
[root@host~]# ovs-ofctl add-flow br0
dl_type=0x800,nw_proto=6,nw_src=10.1.1.66,tp_src=11000,nw_dst=10.1.1.58,tp_d
st=21000,action=mod_nw_src=10.2.2.66,mod_tp_src=11005,mod_nw_dst:10.2.2.62,m
od_tp_dst:12345,output:2
•
Exact-match flow to match 4-tuple IPv6 traffic and do NAT rewrite:
[root@host~]# ovs-ofctl add-flow br0
in_port=1,dl_type=0x86dd,nw_proto=6,ipv6_src=2000::66,tp_src=11000,ipv6_dst=
2000::58,tp_dst=11000,action=set_field:2001::66-
\>ipv6_src,mod_tp_src=15000,output:2
•
Wild-card flow to drop fragmented packets:
[root@host~]# ovs-ofctl add-flow br0 dl_type=0x800,ip_frag=yes,action=drop
•
Exact-match flow to switch 4-tuple IPv4 traffic with TOS 0xE0:
[root@host~]# ovs-ofctl add-flow br0 in_port=1,dl_type=0x800,nw_proto=6,
nw_src=10.1.1.66,tp_src=11000,nw_dst=10.1.1.58,tp_dst=21000,
nw_tos=0xE0,action=output:2
•
If a wild-card and exact match flow both exist for the same traffic pattern, the flow that is
created first will take priority. In the below example, the wild-card flow will take priority as
it was created first.
[root@host~]# ovs-ofctl add-flow br0
dl_type=0x800,nw_src=10.1.1.58,nw_dst=10.1.1.66,tp_src=15000,tp_dst=15000,ac
tion=output:1
[root@host~]# ovs-ofctl add-flow br0
dl_type=0x800,nw_proto=6,nw_src=10.1.1.58,nw_dst=10.1.1.66,tp_src=15000,tp_d
st=15000,action=output:1
3.2.1.2. VLAN Flows
Below are few example VLAN flows with the following FilterMode and FiletrMask combination.
filterMode = fragmentation,mpshittype,ethertype,vlan,port
filterMask = ethertype,vlan,port
Reload cxgb4 driver after updating filterMode and filterMask .