* Re: Bug with GRE tunnel and "ip xfrm" GRE match?
[not found] ` <CAFXBA=nu9tFA=5r8iXW2CVNxhTuQDXgqJr30mEbMPydC8YBjYQ@mail.gmail.com>
@ 2017-10-18 7:14 ` Harsh Jain
2017-10-18 7:14 ` Harsh Jain
1 sibling, 0 replies; 2+ messages in thread
From: Harsh Jain @ 2017-10-18 7:14 UTC (permalink / raw)
To: Keith Holleman, netdev; +Cc: ovs-discuss, ovs-dev
Also sdding netdev for more inputs.
On Wed, Oct 18, 2017 at 12:13 PM, Harsh Jain <harshjain.prof@gmail.com> wrote:
> Hi keith,
>
> Its being a long time when I observed this issue. What I remember is ,
> The kernel patch which I shared was not compatible with latest kernel.
> there after I switched to another project, Didn't get chane to
> re-produce the issue. It is an OVS bug. I am adding ovs Dev team may
> be they can help you out.
>
> Regards
> Harsh Jain
>
> On Wed, Oct 18, 2017 at 5:19 AM, Keith Holleman
> <holleman@skyportsystems.com> wrote:
>>
>> Does anyone know the status of this problem? The code has changed from the
>> original proposed patch but I don't think I see it fixed as of yet.
>>
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2015-June/037681.html
>>
>> I can't find an issue that was ever raised to track this either.
>>
>> The reason I'm asking is that I have run into what seems to be very similar
>> behavior where an installed "ip xfrm" policy that attempts to match on GRE
>> keys but does not seem to work when the GRE packet is generated by a local
>> OVS switch.
>>
>> -K
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug with GRE tunnel and "ip xfrm" GRE match?
[not found] ` <CAFXBA=nu9tFA=5r8iXW2CVNxhTuQDXgqJr30mEbMPydC8YBjYQ@mail.gmail.com>
2017-10-18 7:14 ` Bug with GRE tunnel and "ip xfrm" GRE match? Harsh Jain
@ 2017-10-18 7:14 ` Harsh Jain
1 sibling, 0 replies; 2+ messages in thread
From: Harsh Jain @ 2017-10-18 7:14 UTC (permalink / raw)
To: Keith Holleman, netdev; +Cc: ovs-discuss, ovs-dev
Also sdding netdev for more inputs.
On Wed, Oct 18, 2017 at 12:13 PM, Harsh Jain <harshjain.prof@gmail.com> wrote:
> Hi keith,
>
> Its being a long time when I observed this issue. What I remember is ,
> The kernel patch which I shared was not compatible with latest kernel.
> there after I switched to another project, Didn't get chane to
> re-produce the issue. It is an OVS bug. I am adding ovs Dev team may
> be they can help you out.
>
> Regards
> Harsh Jain
>
> On Wed, Oct 18, 2017 at 5:19 AM, Keith Holleman
> <holleman@skyportsystems.com> wrote:
>>
>> Does anyone know the status of this problem? The code has changed from the
>> original proposed patch but I don't think I see it fixed as of yet.
>>
>> https://mail.openvswitch.org/pipermail/ovs-discuss/2015-June/037681.html
>>
>> I can't find an issue that was ever raised to track this either.
>>
>> The reason I'm asking is that I have run into what seems to be very similar
>> behavior where an installed "ip xfrm" policy that attempts to match on GRE
>> keys but does not seem to work when the GRE packet is generated by a local
>> OVS switch.
>>
>> -K
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-10-18 7:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAJU4r8qBM5dy3B7+vQEBbUKQB0vE0B+aAtkp0_2p3P9t1hZ4gw@mail.gmail.com>
[not found] ` <CAFXBA=nu9tFA=5r8iXW2CVNxhTuQDXgqJr30mEbMPydC8YBjYQ@mail.gmail.com>
2017-10-18 7:14 ` Bug with GRE tunnel and "ip xfrm" GRE match? Harsh Jain
2017-10-18 7:14 ` Harsh Jain
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.