On Mon, Jun 25, 2012 at 5:40 PM, ravi kerur <rke...@gmail.com> wrote: > On Mon, Jun 25, 2012 at 3:33 PM, Jesse Gross <je...@nicira.com> wrote: >> On Thu, Jun 21, 2012 at 2:54 PM, ravi kerur <rke...@gmail.com> wrote: >>> I would like to restart this discussion as I am having trouble with >>> configuration + performance. I would like send just tcp traffic via >>> gre tunnel and would like to push a vlan tag before sending via gre >>> tunnel. On receive side after gre decapsulation, match should happen >>> on vlan_vid and configured actions executed. I don't think it is >>> possible to do this in ovs currently based on what you had described >>> earlier in another thread, but just want to check again if its indeed >>> possible then how the flows should be configured on receive side. >>> >>> On Tx side I have flows configured to match (gre_port = 2, eth_port = 1) >>> >>> dl_type=0x0800, nw_proto=6, nw_src=<src-ip>,nw-dst=<dst-ip>, >>> actions=mod_vlan_vid:100,mod_vlan_pcp:4,2 >>> dl_type=0x0800, nw_proto=47, nw_src=<src-ip>, nw-dst=<dst-ip>, actions=1 >>> >>> via tcpdump I see vlan packets encapsulated in gre header. >>> >>> on Rx side, I had configured >>> >>> dl_type=0x0800,nw_proto=47,nw_src=<dst-ip>, nw-dst=<src-ip>, >>> actions=resubmit:2 >>> in_port=2,dl_vlan_vid;100,dl_vlan_pcp:4,actions=strip_vlan,0 >> >> This flow doesn't decapsulate the packet, it just matches on the fact >> that it is GRE. If you want to decapsulate it, you should use a GRE >> vport. >> > > <rk> use GRE vport where? in actions or flow-matching? I had tried it > in actions by setting actions=2 and in didn't work. Are there example > configuration for this, it will be really helpful? I didn't see any on > openvswitch website.
Here's one tutorial: http://networkstatic.net/2012/04/open-vswitch-gre-tunnel-configuration/ _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
