RHEL: sending reset with wrong sequence number which is ignored so connection is not reset

Solution In Progress - Updated -

Issue

  • Red Hat Enterprise Linux is sending a reset with a sequence number that has already been acknowledged so it is ignored. This results in the local host (also Red Hat Enterprise Linux) continuing to send packets.

Environment

  • Client: Red Hat Enterprise Linux (Could really be any type of host)
  • Server: Red Hat Enterprise Linux
  • separated by some kind of state-full packet filtering device (probably a firewall)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.