I’m trying to get flow-mode tunneling working with native GRE tunneling.  I 
have a 2 port switch, access and trunk (tunnel) with the 2 ports connected to 
test gear. The problem is that the trunk-to-access direction is not working. It 
looks like packets are egressing from b1 on port NORMAL, where they disappear.

When I configure port-mode tunneling, everything works and I notice that b1 
does not egress to port NORMAL but ingresses directly to b0 from b1.

Another observation is that when it is working for port mode tunneling, the 
call to “tnl_port_should_receive” in function “xlate_lookup_ofproto_”
sometimes return “true”. For flow mode tunneling, this function always returns 
“false”.

Here is my flow mode configuration.
I was wondering if you could spot anything obviously wrong or if this is a 
known issue.



## Flow-based GRE Tunnel

## Access Side
##
ovs-vsctl add-br b0  -- set bridge b0 datapath_type=netdev
ovs-vsctl add-port b0 gre0 -- set Interface gre0 type=gre 
options:remote_ip=flow options:key=flow
ovs-vsctl add-port b0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl set Interface gre0 ofport_request=1
ovs-vsctl set Interface dpdk0 ofport_request=2
ifconfig b0 10.10.20.40 netmask 255.255.255.0

## Output Bridge:
## Tunnel Side
##
ovs-vsctl add-br b1  -- set bridge b1 datapath_type=netdev
ovs-vsctl add-port b1 dpdk1 -- set Interface dpdk1 type=dpdk
ovs-vsctl set Interface dpdk1 ofport_request=1
ifconfig b1  10.10.10.40 netmask 255.255.255.0

## Set up flows:

## Access
##
# in dpdk0, out gre
ovs-ofctl add-flow b0 "in_port=2 
action=set_tunnel:123,set_field:10.10.10.2->tun_dst,output:NORMAL"

# in gre, out dpdk0
ovs-ofctl add-flow b0 "in_port=1,tun_src=10.10.10.2,tun_id=123,action=output:2"

## Tunnel
##
# in linux, out dpdk2
ovs-ofctl add-flow b1 in_port=LOCAL,action=output:1

# in dpdk2, out linux
ovs-ofctl add-flow b1 in_port=1,action=output:NORMAL


Best regards and thanks,

David




This email and attachments may contain privileged or confidential information 
intended only for the addressee(s) indicated. The sender does not waive any of 
its rights, privileges or protections respecting this information. If you are 
not the named addressee, an employee, or agent responsible for sending this 
message to the named addressee (or this message was received by mistake), you 
are not authorized to read, print, retain, copy or disseminate this message or 
any part of it. If received in error, please notify us immediately by e-mail, 
discard any paper copies and delete all electronic files of the email.

Computer viruses can be transmitted via email. The recipient should check this 
email and any attachments for viruses. Email transmission cannot be guaranteed 
to be secured or error-free as information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. The sender 
accepts no liability for any damage caused by any transmitted viruses or errors 
or omissions in the contents of this message.

Overture Networks, Inc. 637 Davis Drive, Morrisville, NC USA 27560 
www.overturenetworks.com
_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to