Hi Yinpeijun,
On Tue, 2014-05-13 at 02:13 +, Yinpeijun wrote:
> >Date: Thu, 19 Dec 2013 14:45:33 +0100
> >From: Igor Sever
> >Subject: Re: [ovs-discuss] VXLAN problems
> >To: Jesse Gross
> >Cc: "discuss@openvswitch.org"
> >Message-ID:
> >
> >Content-Type: text/plain; charset="iso-8859-
>Date: Thu, 19 Dec 2013 14:45:33 +0100
>From: Igor Sever
>Subject: Re: [ovs-discuss] VXLAN problems
>To: Jesse Gross
>Cc: "discuss@openvswitch.org"
>Message-ID:
>
>Content-Type: text/plain; charset="iso-8859-1"
>
>I managed to solve this by setting VM NIC MTU to 1400, 1450 wasn't enough.
On Mon, May 12, 2014 at 2:04 PM, Andrey Korolyov wrote:
> On Tue, May 13, 2014 at 12:58 AM, Jesse Gross wrote:
>> On Sat, May 10, 2014 at 2:13 PM, Andrey Korolyov wrote:
>>> Hello,
>>>
>>> sorry for bringing this old thread on top, but right now building
>>> against current RHEL 3.10.121.el7 see
On Tue, May 13, 2014 at 12:58 AM, Jesse Gross wrote:
> On Sat, May 10, 2014 at 2:13 PM, Andrey Korolyov wrote:
>> Hello,
>>
>> sorry for bringing this old thread on top, but right now building
>> against current RHEL 3.10.121.el7 seems not possible without
>> patchwork. After fixing some obvious
On Sat, May 10, 2014 at 2:13 PM, Andrey Korolyov wrote:
> Hello,
>
> sorry for bringing this old thread on top, but right now building
> against current RHEL 3.10.121.el7 seems not possible without
> patchwork. After fixing some obvious kversion checks and code
> snippets, I had stuck on f06798797
