<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Header on Aaron&#39;s Worthless Words</title>
    <link>https://38a8db03.aww-3cz.pages.dev/tags/header/</link>
    <description>Recent content in Header on Aaron&#39;s Worthless Words</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 23 Jun 2011 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://38a8db03.aww-3cz.pages.dev/tags/header/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Frame Relay Notes - LMI, Headers, and Encapsulation</title>
      <link>https://38a8db03.aww-3cz.pages.dev/posts/2011/06/frame-relay-notes-lmi-headers-and-encapsulation/</link>
      <pubDate>Thu, 23 Jun 2011 00:00:00 +0000</pubDate>
      <guid>https://38a8db03.aww-3cz.pages.dev/posts/2011/06/frame-relay-notes-lmi-headers-and-encapsulation/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Local Management Interface&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Manages link between the router and frame relay switch&lt;/li&gt;&#xA;&lt;li&gt;Routers send &lt;em&gt;Status Enquiry&lt;/em&gt; to the switch&lt;/li&gt;&#xA;&lt;li&gt;The switch responds with a &lt;em&gt;Status&lt;/em&gt; message informing the router of the DLCIs available&lt;/li&gt;&#xA;&lt;li&gt;Serves as a keepalive&lt;/li&gt;&#xA;&lt;li&gt;Default keepalive is 10 seconds, 3 misses is failed&lt;/li&gt;&#xA;&lt;li&gt;Three types&#xA;&lt;ul&gt;&#xA;&lt;li&gt;cisco &amp;lt;- default&lt;/li&gt;&#xA;&lt;li&gt;ansi (Annex D)&lt;/li&gt;&#xA;&lt;li&gt;q933a&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code data-lang=&#34;fallback&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config)#interface s1/0&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config-if)#frame-relay lmi-type ansi&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Headers and Encapsulation&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Link Access Procedure for Frame-mode Bearer Services (LAPF) is the first header&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Includes DLCI, DE, FECN, BECN&lt;/li&gt;&#xA;&lt;li&gt;To be read by the frame relay switch&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Frame relay encapsulation header is next&#xA;&lt;ul&gt;&#xA;&lt;li&gt;To be read by the router on the other end of the VC&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;Two types&#xA;&lt;ul&gt;&#xA;&lt;li&gt;cisco : proprietary &amp;lt;- default&lt;/li&gt;&#xA;&lt;li&gt;ietf : IETF RFC 2427&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code data-lang=&#34;fallback&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config)#interface s1/0&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config-if)#frame-relay encapsulation ietf &amp;lt;- for all DLCIs&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;- or -&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config-if)#frame-relay interface-dlci 100 ietf &amp;lt;- for specific DLCIs&#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;- or - &#xA;&lt;/span&gt;&lt;/span&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;R1(config-if)#frame-relay map ip 10.0.0.1 ietf &amp;lt;- for specific DLCis&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Wireshark and EtherIP Packets</title>
      <link>https://38a8db03.aww-3cz.pages.dev/posts/2011/06/wireshark-and-etherip-packets/</link>
      <pubDate>Sat, 04 Jun 2011 00:00:00 +0000</pubDate>
      <guid>https://38a8db03.aww-3cz.pages.dev/posts/2011/06/wireshark-and-etherip-packets/</guid>
      <description>&lt;p&gt;I got a call from our Systems and Security guys today to talk about a Wireshark capture they had done from a user VLAN.  They had noticed two frames that were destined for some seemingly random host in the same network as they were in, but the source and destination IP addresses reported by Wireshark made no sense.  The frames were from a web server to an IP address on our wireless network.  The web server is on the other side of the firewall, and the wireless network is on the other side of the controller; there was no reason at all that a packet with that source and destination would show up here.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Network Protocol Overhead</title>
      <link>https://38a8db03.aww-3cz.pages.dev/posts/2011/01/network-protocol-overhead/</link>
      <pubDate>Mon, 10 Jan 2011 00:00:00 +0000</pubDate>
      <guid>https://38a8db03.aww-3cz.pages.dev/posts/2011/01/network-protocol-overhead/</guid>
      <description>&lt;p&gt;Here are some packet overhead numbers for a few popular protocols to help with doing bandwidth requirement calculations.  This may be another add-as-we-go post, so please comment with additions or corrections.&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Ethernet : 20 bytes&lt;br&gt;&#xA;Frame Relay : 4 - 6 bytes&lt;br&gt;&#xA;PPP : 6 bytes&lt;br&gt;&#xA;MLPPP: 10 bytes&lt;br&gt;&#xA;MPLS : 4 bytes&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;IP : 20 bytes&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;TCP : 20+ bytes&lt;br&gt;&#xA;UDP : 8 bytes&lt;br&gt;&#xA;GRE:  4 - 20+ bytes&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
