22d4f4c1   
   From: rick.jones2@hp.com   
      
   Madhur  wrote:   
   > Yes...indeed it was not the problem with jubmo frames. but was   
   > problem with offloading.   
      
   > "ethtook -K  gro off" has done the trick. Issue is   
   > resolved.   
      
   One of the reasons GRO (in the stack) was created vs LRO (in the NIC   
   hardware) was to be able to preserve the original segmenting when the   
   system was being used to forward traffic (L3 or L2).  I suppose your   
   kernel version may have something amiss in that area, but if you can,   
   you might try a later/latest kernel, see if you still need to disable   
   GRO there, and if so, bring that to the attention of the Linux   
   networking developers/maintainers.   
      
   rick jones   
   --   
   The glass is neither half-empty nor half-full. The glass has a leak.   
   The real question is "Can it be patched?"   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)