<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:foaf="https://xmlns.com/foaf/0.1/" xmlns:og="https://ogp.me/ns#" xmlns:rdfs="https://www.w3.org/2000/01/rdf-schema#" xmlns:schema="https://schema.org/" xmlns:sioc="https://rdfs.org/sioc/ns#" xmlns:sioct="https://rdfs.org/sioc/types#" xmlns:skos="https://www.w3.org/2004/02/skos/core#" xmlns:xsd="https://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/october">
  <channel>
    <title>october</title>
    <link>https://www.linuxjournal.com/tag/october</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>October 2011 Issue of Linux Journal: Networking</title>
  <link>https://www.linuxjournal.com/content/october-2011-issue-linux-journal-networking</link>
  <description>  &lt;div data-history-node-id="1025701" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/cover210.jpg" width="200" height="267" alt="October 2011 issue of Linux Journal cover image: Networking" title="October 2011 issue of Linux Journal: Networking" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/shawn-powers" lang="" about="https://www.linuxjournal.com/users/shawn-powers" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Shawn Powers&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;SneakerNets and BNC Terminators&lt;/p&gt;
&lt;p&gt;I  first started my sysadmin career about the time in history when 10BASE2  was beginning to see widespread adoption. ThinNet, as it also was  called, meant an affordable transition from the SneakerNet so many  businesses used. (SneakerNet is a term for walking floppy disks back and  forth between computers—not really a network, but it’s how data was  moved.) Anyone who remembers those years knows ThinNet was extremely  vulnerable to system-wide failures. A single disconnect (or stolen BNC  terminator cap at the end of the chain) meant the entire network was down. That was a small price to pay for such inexpensive and  blazing-fast speed. 10Mbit was the max speed ThinNet supported, but who  in the world ever would need that much throughput?&lt;/p&gt;
&lt;p&gt;Networking  has changed a lot since my career started, and it’s issues like this  one that keep me up to date. &lt;a href="https://www.linuxjournaldigital.com/linuxjournal/201110/?pg=36&amp;pm=2&amp;u1=friend"&gt;Kyle Rankin starts off with a hacking  primer using an off-the-shelf home router&lt;/a&gt; (follow this link to read the full article now-- it's open to all as a free preview of this October issue). This isn’t merely the old  WRT54G hacks you’re used to reading about. Instead, Kyle shows us how to  don our black hats and really hack in to a D-Link wireless 802.11n  router. If Kyle’s hacking tutorial makes you a little nervous, don’t  worry; we have some network security this month as well. Henry Van Styn  teaches us some advanced firewall configurations with ipset. Granted,  firewalls won’t protect anyone from PHP vulnerabilities, but they still  help me sleep better at night.&lt;/p&gt;
&lt;p&gt;Mike  Diehl switches gears, and instead of showing how to hack (or protect)  the network, he describes how to create. Specifically, he explains how  to create network programs that are cross-platform and easy to build  with ENet. As someone whose programming skills peaked with 10 GOTO 10,  Mike’s idea of “easy” might be relative, but he gives coding examples,  so even copy/paste programmers can join in.&lt;/p&gt;
&lt;p&gt;Henry  Van Styn has another article in this issue on how to use tcpdump to  troubleshoot network issues effectively. If you’re in charge of a large  network, you owe it to yourself to polish your tcpdump skills. It’s a  tool every network administrator needs, and Henry takes some of the  mystery out of it. Adrian Hannah follows in a one-two punch teaching us  how to sniff packets effectively. Packet sniffing is one of those skills  that can be used for good and evil both, but we’ll assume you’ll use  your powers for good. At the very least, you’ll understand what sort of  information is available on your network so you can try to secure it a  bit.&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/october-2011-issue-linux-journal-networking" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Tue, 11 Oct 2011 19:27:05 +0000</pubDate>
    <dc:creator>Shawn Powers</dc:creator>
    <guid isPermaLink="false">1025701 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
