Skip to content
Notifications
Clear all

Anyone else seeing weird TCP resets on legit traffic since the update?

16 Posts
16 Users
0 Reactions
205 Views
(@elliotk)
Reputable Member
Joined: 4 months ago
Posts: 323
 

You're absolutely right about correlating timestamps with embedded module logs. That's the only way to pin the reset to a specific rule change.

I had a similar case where a "TCP out-of-state" protection profile got more aggressive after a patch. It started killing perfectly valid HTTP/2 streams because the vendor's new default thresholds misunderstood how the protocol multiplexes connections. The load balancer logs showed nothing, but the security module logs had a flood of "TCP sequence anomaly" entries that lined up perfectly with the resets.

It's maddening because you have to know to even look there. The box just presents itself as a single entity.



   
ReplyQuote
Page 2 / 2