<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>4-Tuple on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/4-tuple/</link>
    <description>Recent content in 4-Tuple on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <image>
      <title>Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
      <url>https://netacoding.com/img/logo-netacoding.png</url>
      <link>https://netacoding.com/img/logo-netacoding.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/4-tuple/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TCP State Exhaustion: TIME_WAIT Flood, Sockstress Persist Timer Abuse &amp; Conntrack DoS | Linux Kernel</title>
      <link>https://netacoding.com/posts/tcp-state-exhaustion/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/tcp-state-exhaustion/</guid>
      <description>TCP connection capacity is bounded by 4-tuple uniqueness and kernel conntrack table size — not port numbers. Covers TIME_WAIT socket exhaustion, Sockstress (window=0 &#43; Persist Timer loop, 2008), Slowloris-class L7 variants, ip_conntrack_max limits, and net.ipv4.tcp_tw_reuse/tcp_fin_timeout tuning for defense.</description>
    </item>
  </channel>
</rss>
