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@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@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 <[email protected]> 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. > > _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
