The patch works. Thanks for that. One other anomaly I noticed when displaying tunnel ports:
## port-mode tunnel port, looks good. ## ovs-appctl tnl/ports/show Listening ports: gre_sys (2) : eth_type(0x0800),ipv4(proto=47,frag=no) ## flow-mode tunnel port, port type is garbled ## ovs-appctl tnl/ports/show Listening ports: ��� (2) : eth_type(0x0800),ipv4(proto=47,frag=no) -----Original Message----- From: Jesse Gross [mailto:[email protected]] Sent: Wednesday, June 24, 2015 6:00 PM To: David Griswold Cc: [email protected] Subject: Re: [ovs-discuss] Flow-Mode Userspace GRE Tunneling On Wed, Jun 24, 2015 at 1:40 PM, David Griswold <[email protected]> wrote: > 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. I think I see the problem, a check from port based tunneling was carried over to the more general native tunneling case. I just sent out a patch, can you please try it out? > 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”. This check only tests to see if a flow has tunnel IP addresses, which should be true for all decapsulated packets. I guess you are probably looking at this on the physical bridge, where the packet hasn't been decapsulated yet? The "sometimes" for port based tunnels would depend on whether the packet has been decapsulated yet and the never for flow based tunnels is because the process fails before decapsulation. 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
