<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protocol on csegura</title><link>https://blog.romheat.net/tags/protocol/</link><description>Recent content in Protocol on csegura</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 30 Aug 2026 12:01:00 +0100</lastBuildDate><atom:link href="https://blog.romheat.net/tags/protocol/index.xml" rel="self" type="application/rss+xml"/><item><title>The rmtdos Protocol: V1, My Improvements, and V2</title><link>https://blog.romheat.net/posts/2026/26_08_30_rmtdos_protocol_v1_improvements_and_v2/</link><pubDate>Sun, 30 Aug 2026 12:01:00 +0100</pubDate><guid>https://blog.romheat.net/posts/2026/26_08_30_rmtdos_protocol_v1_improvements_and_v2/</guid><description>&lt;p>This is a companion to the &lt;a href="https://blog.romheat.net/posts/2026/26_08_30_rmtdos_0_2_remote_dos_over_ethernet/">article about rmtdos 0.2&lt;/a>, where I show what the fork adds. Here I go deeper into the protocol. I explain V1, the original one by Dennis Jenkins. Then I tell the improvements that I made to the V1 server on an XT and a 386. And at the end I describe V2, which replaces how the screen is sent.&lt;/p>
&lt;h2 id="the-frame">The frame&lt;/h2>
&lt;p>rmtdos does not use IP. Every packet is a raw Ethernet frame with the EtherType &lt;code>80AB&lt;/code>, an rmtdos header of 12 bytes and a payload. All multi-byte numbers are big endian.&lt;/p></description></item></channel></rss>