[ovs-discuss] Anybody knows how we can dynamically change vxlan dst_port by openflow load, move or set_field action?
a.medhat.h at gmail.com
Wed Nov 30 15:43:29 UTC 2016
I also face that problem in my OPNFV APEX deployment. I hope, it is fixed
On Sat, Nov 26, 2016 at 11:08 PM, Ben Pfaff <blp at ovn.org> wrote:
> On Thu, Nov 24, 2016 at 02:39:43AM +0000, 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 forward the packet from the first vxlan port to the
> second one, we need the packet should be sent out with the second vxlan
> port's dst_port as tp_dst, but current vxlan module will use that one from
> the first vxlan port, the source code in vxlan module and our experiment
> have confirmed this.
> > The line in file datapath/linux/compat/vxlan.c is here:
> > dst_port = info->key.tp_dst ? : vxlan->cfg.dst_port;
> > Anybody knows how we can change this? The below change seems more
> reasonable to me, or do we have some ways to dynamically change it by
> openflow actions?
> > dst_port = vxlan->cfg.dst_port ? : info->key.tp_dst;
> I think that this might be related to the bug that Gerhard reported,
> starting here:
> Gerhard, does Yang's fix make any difference for you? (I don't know
> whether you're using the compat code, but the upstream code may have the
> same bug.)
> discuss mailing list
> discuss at openvswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss