Re: [ovs-discuss] Subsequent packets get lost

2015-04-27 Thread Peter Bryzgalov
Hi, Thank you, Gowrishankar! MTU 1450 perfectly worked for vxlan! Regards, Peter ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss

Re: [ovs-discuss] Subsequent packets get lost

2015-04-27 Thread gowrishankar
On Monday 27 April 2015 07:56 PM, Pyotr Bryzgalov wrote: Thank you Gowrishankar, I had MTU 1500. I set tap interfaces’ MTU to 1462 and it worked for GRE tunnel! Unfortunately, setting MTU to 1458 (1500 - 14 - 20 - 8) does’t work for VXLAN. (8 bytes is vxlan header size) In case of GRE: ou

Re: [ovs-discuss] Subsequent packets get lost

2015-04-27 Thread Pyotr Bryzgalov
Thank you Gowrishankar, I had MTU 1500. I set tap interfaces’ MTU to 1462 and it worked for GRE tunnel! Unfortunately, setting MTU to 1458 (1500 - 14 - 20 - 8) does’t work for VXLAN. (8 bytes is vxlan header size) Regards, Peter > On 27Apr, 2015, at 19:59, gowrishankar > wrote: > > On Mo

Re: [ovs-discuss] Subsequent packets get lost

2015-04-27 Thread gowrishankar
On Monday 27 April 2015 04:03 PM, Peter Bryzgalov wrote: Hi, I have connected two Docker containers on two hosts through an OVS tunnel (tested GRE and VXLAN). I can ping and even login with ssh from one container to another through the tunnel, but I cannot use scp, iperf, etc., because for st

[ovs-discuss] Subsequent packets get lost

2015-04-27 Thread Peter Bryzgalov
Hi, I have connected two Docker containers on two hosts through an OVS tunnel (tested GRE and VXLAN). I can ping and even login with ssh from one container to another through the tunnel, but I cannot use scp, iperf, etc., because for streams only the first packet reaches destination and all sub