Menu

#3 [FIXED} Custom Header Size to Decapsulate

0.9
closed
fixed (1)
2019-02-02
2019-01-24
No

Hello RCDCap Team,

I have a question about decapsulating headers based on custom size. For Example, in our environment the ERSPAN header size is 38 bytes instead of 50 bytes, I have confirmed that using editcap utility on CentOS-7, when I take off 38 bytes off I can see actual SPAN traffic instead of GRE tunnel traffic. When I use RCDCap to decapsulate it takes some extra bytes of and loose Ether and IP headers. Is there a way to hardcore static length, e.g. 38 bytes, to decapsulate ERSPAN with RCDCap? Unfortunately, I cannot share PCAP due to organization policy. Please advise.

Discussion

  • Zero effect

    Zero effect - 2019-01-27

    Another user (Walter Shoeber) suggested a patch for Juniper routers. I just commited slightly altered version in the Mercurial repo. Can you test it and say whether it fixes your issue?

     
  • Jawad Rajput

    Jawad Rajput - 2019-01-27

    Thank you very much. I will try and let you know how it goes, I just want to confirm that I am replacing erspan-processor.cc and then recomplie rpm for CentOS-7, right? Or can I just replace erspan-processor.cc on already installed system?

     
  • Zero effect

    Zero effect - 2019-01-27

    yes, you need to recompile

     
  • Jawad Rajput

    Jawad Rajput - 2019-01-28

    it worked, thanks a lot.

     
  • Zero effect

    Zero effect - 2019-02-02
    • assigned_to: Zero effect
     
  • Zero effect

    Zero effect - 2019-02-02
    • labels: --> fixed
    • summary: Custom Header Size to Decapsulate --> [FIXED} Custom Header Size to Decapsulate
    • status: open --> closed
     

Log in to post a comment.