[ovs-discuss] OVS

Ammu ammukeerthu at gmail.com
Wed Mar 20 18:15:48 UTC 2019


Will do, thanks!

-Keerthana

On Wed, 20 Mar 2019 23:39 Ben Pfaff, <blp at ovn.org> wrote:

> 2.9.0 is also old, even in the 2.9.x series 2.9.4 has been released.  If
> you're going to use an old release branch please at least use the latest
> version from that branch.
>
> On Wed, Mar 20, 2019 at 11:01:53PM +0530, Ammu wrote:
> > Hi Pfaff,
> >
> > Thanks for suggesting.
> >
> > I had another setup with following configuration. Still I see the same.
> DF
> > bit set.
> >
> > Linux Version 3.10.0-862.11.6.el7.x86_64
> > Red Hat Enterprise Linux Server release 7.5 (Maipo)
> > OvS version 2.9.0
> >
> > Is that okay? If not, I will pull out the latest version of OvS and will
> > update you on that tomorrow.
> >
> > -
> > Keerthana
> >
> > On Wed, 20 Mar 2019 21:36 Ben Pfaff, <blp at ovn.org> wrote:
> >
> > > I'd suggest upgrading.  Open vSwitch 2.7.0 is too old.  Even within the
> > > 2.7.x series, the latest version is 2.7.8.  It is a waste of our time
> to
> > > try to try to debug a problem that might already have been fixed.
> > >
> > > On Wed, Mar 20, 2019 at 04:34:45PM +0530, Ammu wrote:
> > > > Hi Pfaff,
> > > >
> > > > Thank you for your response.
> > > >
> > > > Here are the requirements you requested for:
> > > >
> > > > [root at localhost ~]# uname -a
> > > > Linux localhost.localdomain 3.10.0-514.el7.x86_64 #1 SMP Tue Nov 22
> > > > 16:42:41 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> > > >
> > > > [root at localhost ~]# ovs-vsctl show
> > > > 0278e2a3-3c9f-4102-9449-65e3710cb5ad
> > > >     ovs_version: "2.7.0"
> > > >
> > > > -
> > > > Keerthana
> > > >
> > > >
> > > > On Wed, Mar 20, 2019 at 6:56 AM Ben Pfaff <blp at ovn.org> wrote:
> > > >
> > > > > On Tue, Mar 19, 2019 at 05:19:42PM +0530, Ammu wrote:
> > > > > >
> > > > >
> > >
> https://stackoverflow.com/questions/55223517/allow-df-not-to-be-set-on-gre-vxlan-tunnels
> > > > >
> > > > > That question reads:
> > > > >
> > > > >     I have created a bridge with a tunnel interface(be it either
> > > > >     vxlan/gre) and an internal interface. When incoming packets get
> > > > >     encapsulated with either vxlan/gre tunnel header, I don't want
> the
> > > > >     DF bit set on the outer IP layer of tunnelled packet.
> > > > >
> > > > >     Despite setting df_default tunnel option to False while
> creating
> > > the
> > > > >     tunnel interface, I get the DF bit set on the outer IP layer
> of the
> > > > >     tunnelled packet.
> > > > >
> > > > > Glancing through the userspace and datapath code in the tree, it
> looks
> > > > > to me like the DF setting propagates through the whole stack, so
> I'm
> > > > > surprised there's a bug.  Perhaps Greg can take a look at some
> point,
> > > if
> > > > > he has time.
> > > > >
> > > > > We probably need to know what version of OVS you're using, what
> version
> > > > > of the kernel you're running, and whether you're using the Linux
> kernel
> > > > > built-in version of the OVS kernel module or the one that is
> shipped
> > > > > with OVS itself.
> > > > >
> > >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20190320/4e1e0eeb/attachment-0001.html>


More information about the discuss mailing list