[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMhzB3UzfeJ8rvCmDFG57QnG5wdHPfahthxgR7Y-vvaiQg@mail.gmail.com>
Date: Sun, 29 Nov 2015 15:37:26 +0200
From: Or Gerlitz <gerlitz.or@...il.com>
To: Joe Stringer <joestringer@...ira.com>,
Jesse Gross <jesse@...nel.org>
Cc: Or Gerlitz <ogerlitz@...lanox.com>, Jesse Gross <jesse@...ira.com>,
Haggai Eran <haggaie@...lanox.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Ilya Lesokhin <ilyal@...lanox.com>,
Rony Efraim <ronye@...lanox.com>,
Hadar Hen Zion <hadarh@...lanox.com>,
Tal Anker <Ankertal@...lanox.com>
Subject: Re: OVS VXLAN decap rule has full match on TTL for the outer headers?
On Thu, Nov 19, 2015 at 5:40 PM, Or Gerlitz <gerlitz.or@...il.com> wrote:
> On Sat, Nov 14, 2015 at 8:45 AM, Joe Stringer <joestringer@...ira.com> wrote:
>> On 13 November 2015 at 06:46, Or Gerlitz <gerlitz.or@...il.com> wrote:
>>> On Fri, Nov 13, 2015 at 10:14 AM, Joe Stringer <joestringer@...ira.com> wrote:
>
>>>> I agree that this UNSPEC issue on v2.3 could do with a bit of a closer
>>>> look. I'll see if I can find some time for it. Alternatively if you're
>>>> willing and have bandwith, I'd be curious if it's related to the
>>>> masked set field feature introduced in Linux-4.0.
>
>>> so what would you suggest here? run with 3.19 or earlier?
>
>> On second thought, I think if it were related to that then userspace
>> v2.4 would not exhibit the problem. I'd have to dig in to see why it
>> occurs.
>
> Any findings?
Hi Joe/Jesse,
Apart from Haggai's note on the TTL, I am pinging you here for the 2nd
time... can you please let me know how
this goes on your end?
Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists