<?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>Packet-Crafting on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/packet-crafting/</link>
    <description>Recent content in Packet-Crafting 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>Fri, 27 Mar 2026 11:25:05 +0300</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/packet-crafting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>RFC 1071 One&#39;s Complement Checksum in x64 Assembly: ICMP Carry Folding, Odd-Byte Handling &amp; Packet Verification</title>
      <link>https://netacoding.com/posts/rfc-1071/</link>
      <pubDate>Fri, 27 Mar 2026 11:25:05 +0300</pubDate>
      <guid>https://netacoding.com/posts/rfc-1071/</guid>
      <description>RFC 1071 checksum computes a 16-bit one&amp;#39;s complement sum over the entire packet in 2-byte chunks. x64 Assembly implementation: word-by-word accumulation loop, odd-byte final block, carry folding via shr/and/add/adc, not ax inversion for final checksum. Required for ICMP packets to pass kernel validation — malformed checksum causes silent drop before delivery.</description>
    </item>
    <item>
      <title>ICMP OS Fingerprinting &amp; NIDS Evasion: Traffic Mimicry via Linux/Windows Payload Signatures in x64 Assembly</title>
      <link>https://netacoding.com/posts/network-fingerprinting/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/network-fingerprinting/</guid>
      <description>Every OS leaves a unique ICMP fingerprint: Linux sends 64-byte payloads with 8-byte RDTSC timestamps, Windows sends 32-byte alphabetical sequences. Covers OS-specific TTL and payload signatures, DPI evasion via traffic mimicry, and x64 Assembly implementation of NIDS-bypassing ICMP packet structures.</description>
    </item>
    <item>
      <title>ICMP Type 3 Protocol Encapsulation: Nested ICMP Firewall Bypass &amp; DPI Evasion via 0xFFFF Boundary Flaw</title>
      <link>https://netacoding.com/posts/icmp_encapsulation/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/icmp_encapsulation/</guid>
      <description>ICMP Type 3 (Destination Unreachable) mandates reflection of the original IP header plus 8 bytes — a field attackers control entirely. Nested ICMP encapsulates secondary protocol headers inside the mandatory reflection segment, bypassing stateful firewalls that classify Type 3 as benign error traffic. 0xFFFF boundary manipulation causes DPI engines to misidentify packet boundaries and skip payload analysis.</description>
    </item>
  </channel>
</rss>
