Outgoing SCTP CRC checksums for packets originating from applications in containers (Docker, OpenShift) or in network namespaces do not get generated

Solution Verified - Updated -

Issue

  • When using an application container or containerized solution such as Docker, Kubernetes, or OpenShift, with an SCTP application running in aforementioned container, checksums at the SCTP frame header do not get generated, and will appear as NULL or "00000000" when viewed with wireshark or tshark.
  • This may throw errors on end applications or hosts that expect valid CRC checksums from the SCTP peer.

Environment

  • Red Hat Enterprise Linux 7.3
  • Upstream Linux Kernel (as of 4.10.0-rc1+)
  • Containerized or network namespaced SCTP application
  • Issue is not present in Red Hat Enterprise Linux 7.2 and prior.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content