Re: PROBLEM: GRE forwarding not working with 3.10.x, WCCPv2 and Cisco 7200 Router showing IP0 bad-hlen 4 in tcpdump

[Peter Schmitt <peter.schmitt82@yahoo.de>]

Hi Pravin,

I tested this patch and it works fine with 3.10.17! Now I get correct packets from the GRE-device and can surf again using WCCP.

Thank you very much!

Best regards,
Peter





> On Friday, October 25, 2013 5:25 PM, Pravin Shelar <pshelar@nicira.com> wrote:
> > Hi Peter,
> I think its easy to fix this case, Can you try attached patch?
> If it works I will send formal patch for stable.
> 
> Thanks,
> Pravin.
> 
> 
> On Fri, Oct 18, 2013 at 4:39 AM, Peter Schmitt <peter.schmitt82@yahoo.de> 
> wrote:
>>  Hi,
>> 
>> 
>> 
>>>  On Thursday, October 17, 2013 3:44 PM, Eric Dumazet 
> <eric.dumazet@gmail.com> wrote:
>>>  > On Thu, 2013-10-17 at 11:53 +0100, Peter Schmitt wrote:
>>>>   Hi,
>>>> 
>>>> 
>>>>   >
>>>>   > 3.10 is buggy (for ETH_P_WCCP support I mean), 3.11 has the 
> probable
>>>>   > fix :
>>>>   >
>>>>   > commit 3d7b46cd20e300bd6989fb1f43d46f1b9645816e
>>>>   > ("ip_tunnel: push generic protocol handling to ip_tunnel
>>>  module.")
>>>>   >
>>>>   > The problem is 3.10 do not pull the extra 4 bytes of WCCP
>>>>   >
>>>>   > This is now properly done in iptunnel_pull_header()
>>>>   >
>>>> 
>>>>   First of all, many thanks for your help on this.
>>>> 
>>>>   I tried to apply the fix to the 3.10.16 sources, as I would like 
> to
>>>>   stay with the long-term line. Unfortunately it does not apply, as
>>>>   there are a lot of dependencies on other patches.
>>>> 
>>>>   Do you think there will be a fix for the long-time 3.10 kernel 
> line?
>>>>   Or can you guide me on how to apply this fix to the long-term 
> kernel?
>>> 
>>>  3.10 is right in the middle of GRE refactoring, and many bugs are in 
> it.
>>> 
>>>  It might be very painful to get a complete list of patches to backport.
>> 
>>  thanks again. Yes I saw that there were lots of changes.
>> 
>>  Do you think there will be a fix for all the 3.10.x stable long term kernel 
> users? Many of them might not be able to use some newer kernel easily or will 
> this be a "won't fix"?
>> 
>>  Best regards,
>>  Peter
>> 
>