TCP adds PSH to many messages in RHEL 9, application cannot determine message boundaries
Issue
- We notice that TCP adds the
PSHflag to many packets in RHEL 9 - Our TCP application cannot determine message boundaries or record markers anymore.
- We noticed in tcpdump and Wireshark a PSH flag is added to the not-last packet of the TCP message. The PSH delivers the message to the next system, but because it doesn't receive the end characters (next TCP segment) it doesn't recognize the message as complete.
Environment
- Red Hat Enterprise Linux 9
- TCP application using
PSHto infer message boundaries or record markers
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
