<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Protocols on unordered</title>
		<link>https://unorde.red/categories/protocols/</link>
		<description>Recent content in Protocols on unordered</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Mon, 18 Feb 2019 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://unorde.red/categories/protocols/feed.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Playing with ICMP and NAT</title>
				<link>https://unorde.red/icmp-and-nat/</link>
				<pubDate>Mon, 18 Feb 2019 00:00:00 +0000</pubDate>
				<guid>https://unorde.red/icmp-and-nat/</guid>
				<description>&lt;p&gt;ICMP stands for Internet Control Message Protocol. It is used by network devices&#xA;to send error messages and operational information. If you&amp;rsquo;ve ever used &lt;code&gt;ping&lt;/code&gt;&#xA;to poke a machine, you&amp;rsquo;ve used the ICMP protocol!&lt;/p&gt;&#xA;&lt;p&gt;The ICMP protocol is very simple. It is considered a layer 3 protocol, and&#xA;messages are wrapped by IP. The header consists of several fields. The first&#xA;byte is a numeric type. For example, 8 is an IPv4 echo request, while 0 is an&#xA;IPv4 echo reply. Next is a code that expands on the type, then a checksum and&#xA;finally 4 bytes that depend on the type/code. For ping, these four bytes consist&#xA;of an identifier and a sequence number. After the header there may be a payload.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Internet 101: TCP</title>
				<link>https://unorde.red/tcp/</link>
				<pubDate>Sat, 04 Nov 2017 00:00:00 +0000</pubDate>
				<guid>https://unorde.red/tcp/</guid>
				<description>&lt;p&gt;&lt;em&gt;This article assumes the reader has basic knowledge of &lt;a href=&#34;https://unorde.red/ip/&#34;&gt;IP&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;IP gives us addressing and the ability to send packets from one machine on the&#xA;internet to another, assuming that routing is configured correctly at each hop.&#xA;However, it provides little else.&lt;/p&gt;&#xA;&lt;p&gt;Imagine trying to send a large file over IP. Due to the length restriction on IP&#xA;packets, the file is broken up into chunks, and each chunk is sent in order as&#xA;an IP packet. In this scenario, any number of things can go wrong. An unreliable&#xA;link may corrupt a packet. A router may choose to route one or more packets&#xA;differently from the others. Packets may be silently dropped or duplicated in&#xA;misconfigured networking devices. Eventually, the destination machine receives&#xA;the packets out of order, with some missing, corrupted or duplicated. Obviously,&#xA;reliably reconstructing the file from these packets is impossible.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Internet 101: IP</title>
				<link>https://unorde.red/ip/</link>
				<pubDate>Sun, 08 Oct 2017 00:00:00 +0000</pubDate>
				<guid>https://unorde.red/ip/</guid>
				<description>&lt;p&gt;The Internet Protocol is responsible for moving data across network boundaries.&#xA;How does it do this?&lt;/p&gt;&#xA;&lt;h3 id=&#34;addressing&#34;&gt;Addressing&lt;/h3&gt;&#xA;&lt;p&gt;To route data on a multi node path from one machine to another, it is necessary&#xA;to uniquely and deterministically identify the source and destination machine&#xA;(it should be noted that this idea is abused a lot in the wild). IP does this by&#xA;defining a numerical IP address.&lt;/p&gt;&#xA;&lt;p&gt;For IPv4, this is a 32 bit number (e.g. 172.16.254.1). Since the number of&#xA;possible IPv4 addresses is grossly insufficient, IPv6 defines a 128 bit number.&#xA;IPv6 addresses are typically shown using eight four-digit hexadecimal numbers&#xA;delimited by colons (e.g. 2001:db8:0:1234:0:567:8:1).&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
