..@ovn.org>;
d...@openvswitch.org; ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Anybody knows how we can dynamically change vxlan
dst_port by openflow load, move or set_field action?
On Sun, Dec 4, 2016 at 5:57 PM, Yang, Yi Y <yi.y.y...@intel.com> wrote:
> Let me
ilto:pshe...@ovn.org]
> Sent: Friday, December 2, 2016 3:54 PM
> To: Yang, Yi Y <yi.y.y...@intel.com>
> Cc: Gerhard Stenzel <gsten...@linux.vnet.ibm.com>; Ben Pfaff <b...@ovn.org>;
> d...@openvswitch.org; ovs-discuss@openvswitch.org
> Subject: Re: [ovs-discuss] Any
ovs-discuss@openvswitch.org
Subject: Re: [ovs-discuss] Anybody knows how we can dynamically change vxlan
dst_port by openflow load, move or set_field action?
On 11/26/2016 11:08 PM, Ben Pfaff wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
>> I noticed vxlan module al
I also face that problem in my OPNFV APEX deployment. I hope, it is fixed
soon.
Best regards,
Ahmed
On Sat, Nov 26, 2016 at 11:08 PM, Ben Pfaff wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
> > I noticed vxlan module always uses tp_dst from tunnel metadata
On 11/26/2016 11:08 PM, Ben Pfaff wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
>> I noticed vxlan module always uses tp_dst from tunnel metadata in preference
>> to vxlan->cfg.dst_port, this isn't the result we want in some use cases, for
>> example, if we create two
On Thu, Nov 24, 2016 at 02:39:43AM +, Yang, Yi Y wrote:
> I noticed vxlan module always uses tp_dst from tunnel metadata in preference
> to vxlan->cfg.dst_port, this isn't the result we want in some use cases, for
> example, if we create two vxlan port which have different dst_port, when we