<div dir="ltr"><div dir="ltr">Hi Pfaff,</div><div dir="ltr"><br></div><div dir="ltr">Thank you for your response.<br><div><br></div><div>Here are the requirements you requested for:</div><div><br></div><div><div>[root@localhost ~]# uname -a</div><div>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</div><div><br></div><div>[root@localhost ~]# ovs-vsctl show</div><div>0278e2a3-3c9f-4102-9449-65e3710cb5ad</div><div> ovs_version: "2.7.0"</div></div><div><br></div><div>-</div><div>Keerthana</div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 20, 2019 at 6:56 AM Ben Pfaff <<a href="mailto:blp@ovn.org">blp@ovn.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Mar 19, 2019 at 05:19:42PM +0530, Ammu wrote:<br>
> <a href="https://stackoverflow.com/questions/55223517/allow-df-not-to-be-set-on-gre-vxlan-tunnels" rel="noreferrer" target="_blank">https://stackoverflow.com/questions/55223517/allow-df-not-to-be-set-on-gre-vxlan-tunnels</a><br>
<br>
That question reads:<br>
<br>
I have created a bridge with a tunnel interface(be it either<br>
vxlan/gre) and an internal interface. When incoming packets get<br>
encapsulated with either vxlan/gre tunnel header, I don't want the<br>
DF bit set on the outer IP layer of tunnelled packet.<br>
<br>
Despite setting df_default tunnel option to False while creating the<br>
tunnel interface, I get the DF bit set on the outer IP layer of the<br>
tunnelled packet.<br>
<br>
Glancing through the userspace and datapath code in the tree, it looks<br>
to me like the DF setting propagates through the whole stack, so I'm<br>
surprised there's a bug. Perhaps Greg can take a look at some point, if<br>
he has time.<br>
<br>
We probably need to know what version of OVS you're using, what version<br>
of the kernel you're running, and whether you're using the Linux kernel<br>
built-in version of the OVS kernel module or the one that is shipped<br>
with OVS itself.<br>
</blockquote></div>