RHEL7: With TCP acceleration module or socket marking the final FIN is not acked

Solution In Progress - Updated -

Issue

  • A particular termination sequence is causing excessive up-link re-transmissions on a customer site due to the failure of the TCP stack to handle it in an expected manner.
  • Socket getting close immediately after FIN_WAIT2. This results in tcp-retransmission for FIN-ACK packets.
  • TCP connections are not terminated correctly.
  • We observe the same footprint when using socket marks for routing.

Environment

  • RHEL 7.3
    • kernel-3.10.0-514.16.1.el7.x86_64
  • 3rd party TCP acceleration module
  • or socket marking, setsockopt(SO_MARK).

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