<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:pingback="http://madskills.com/public/xml/rss/module/pingback/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CLR Hoser - Networking</title>
    <link>http://hoser.lander.ca/</link>
    <description>(none)</description>
    <language>en-us</language>
    <copyright>Rich Lander</copyright>
    <lastBuildDate>Fri, 26 Sep 2008 21:48:51 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.3.9074.18820</generator>
    <managingEditor>rich@lander.ca</managingEditor>
    <webMaster>rich@lander.ca</webMaster>
    <item>
      <trackback:ping>http://hoser.lander.ca/Trackback.aspx?guid=8b737448-f120-4f5f-ba9e-217c8f513b57</trackback:ping>
      <pingback:server>http://hoser.lander.ca/pingback.aspx</pingback:server>
      <pingback:target>http://hoser.lander.ca/PermaLink,guid,8b737448-f120-4f5f-ba9e-217c8f513b57.aspx</pingback:target>
      <dc:creator>Rich Lander</dc:creator>
      <wfw:comment>http://hoser.lander.ca/CommentView,guid,8b737448-f120-4f5f-ba9e-217c8f513b57.aspx</wfw:comment>
      <wfw:commentRss>http://hoser.lander.ca/SyndicationService.asmx/GetEntryCommentsRss?guid=8b737448-f120-4f5f-ba9e-217c8f513b57</wfw:commentRss>
      <slash:comments>1</slash:comments>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <font size="3">I posted last year about the </font>
          <a href="http://hoser.lander.ca/2007/12/04/WiringTheHouseForCAT5e.aspx">
            <font size="3">home
network</font>
          </a>
          <font size="3"> that I had built. It was actually a fair bit of
work and somewhat expensive to get the base network and the initial set of drops setup.
It also required a fair bit of thinking and up-front design to get the network structured
in such a way that it would work for my up-front needs, and then would scale for new
scenarios that I could imagine. It may seem like the task is really simple, and it
kind of is on the face of it. </font>
        </p>
        <p>
          <font size="3">The difficulty is that you need to think through how many CAT5e/6 cables
that you string between major areas of your house. For example, my cable modem and
HDHR devices are in my garage (where my cable comes into the house), my gigE switch,
a bunch of machines and my VOIP box are in my basement, and my wifi AP is
in my attic. That may sound horribly bizarre, but each device is really in the best
location for its purpose, and I needed to ensure that I had enough cable going between
locations to handle the neccessary connectivity.</font>
        </p>
        <p>
          <font size="3">That also doesn't count that I am running voice (voice originating
from my VOIP box) throughout the house over some of these lines, which means that
I have to add another line for analog voice between the major areas of house beyond
what I need for the IP network.</font>
        </p>
        <p>
          <font size="3">My point in this post is that after nearly a year, I decided to add
three more drops on the top floor of the house. Other than the requirement to crawl
into the corners of my attic for one of the drops, it was really, really easy
to tie into the base network that I'd setup months ago. It was very clear what I needed
to do to tie into the network, and it all worked the first time.</font>
        </p>
        <p>
          <font size="3">In addition, I decided to hook up all three of the new drops for data
for now, but it will take me just a few mins to 'downgrade' one of them to voice
should I want to. It is really nice to have that degree of freedom w/o having
to re-wire or otherwise re-do any of the work that I've done. </font>
        </p>
        <img width="0" height="0" src="http://hoser.lander.ca/aggbug.ashx?id=8b737448-f120-4f5f-ba9e-217c8f513b57" />
      </body>
      <title>Extending my home network</title>
      <guid isPermaLink="false">http://hoser.lander.ca/PermaLink,guid,8b737448-f120-4f5f-ba9e-217c8f513b57.aspx</guid>
      <link>http://hoser.lander.ca/2008/09/26/ExtendingMyHomeNetwork.aspx</link>
      <pubDate>Fri, 26 Sep 2008 21:48:51 GMT</pubDate>
      <description>&lt;p&gt;
&lt;font size=3&gt;I posted last year about the &lt;/font&gt;&lt;a href="http://hoser.lander.ca/2007/12/04/WiringTheHouseForCAT5e.aspx"&gt;&lt;font size=3&gt;home
network&lt;/font&gt;&lt;/a&gt;&lt;font size=3&gt; that I had built. It was actually a fair bit of work
and somewhat expensive to get the base network and the initial set of drops setup.
It also required a fair bit of thinking and up-front design to get the network structured
in such a way that it would work for my up-front needs, and then would scale for new
scenarios that I could imagine. It may seem like the task is really simple, and it
kind of is on the face of it. &lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;font size=3&gt;The difficulty is that you need to think through how many CAT5e/6 cables
that you string between major areas of your house. For example, my cable modem and
HDHR devices are in my garage (where my cable comes into the house), my gigE switch,
a bunch of machines&amp;nbsp;and my VOIP box&amp;nbsp;are in my basement, and my wifi AP is
in my attic. That may sound horribly bizarre, but each device is really in the best
location for its purpose, and I needed to ensure that I had enough cable going between
locations to handle the neccessary connectivity.&lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;font size=3&gt;That also doesn't count that I am running voice (voice originating from
my VOIP box) throughout the house over some of these lines, which means that I have
to add another line for analog voice between the major areas of house beyond what
I need for the IP network.&lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;font size=3&gt;My point in this post is that after nearly a year, I decided to add three
more drops on the top floor of the house. Other than the requirement to crawl into
the corners of&amp;nbsp;my attic for one of the drops, it was really, really easy to tie
into the base network that I'd setup months ago. It was very clear what I needed to
do to tie into the network, and it all worked the first time.&lt;/font&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;font size=3&gt;In addition, I decided to hook up all three of the new drops for data
for now, but&amp;nbsp;it will take me just a few mins to 'downgrade' one of them to voice
should I want to. It is really nice to have that degree of&amp;nbsp;freedom w/o having
to re-wire or otherwise re-do any of the work that I've done.&amp;nbsp;&lt;/font&gt;
&lt;/p&gt;
&lt;img width="0" height="0" src="http://hoser.lander.ca/aggbug.ashx?id=8b737448-f120-4f5f-ba9e-217c8f513b57" /&gt;</description>
      <comments>http://hoser.lander.ca/CommentView,guid,8b737448-f120-4f5f-ba9e-217c8f513b57.aspx</comments>
      <category>Networking</category>
    </item>
    <item>
      <trackback:ping>http://hoser.lander.ca/Trackback.aspx?guid=c9cad210-3a70-4536-b94d-118d089a4062</trackback:ping>
      <pingback:server>http://hoser.lander.ca/pingback.aspx</pingback:server>
      <pingback:target>http://hoser.lander.ca/PermaLink,guid,c9cad210-3a70-4536-b94d-118d089a4062.aspx</pingback:target>
      <dc:creator>Rich Lander</dc:creator>
      <wfw:comment>http://hoser.lander.ca/CommentView,guid,c9cad210-3a70-4536-b94d-118d089a4062.aspx</wfw:comment>
      <wfw:commentRss>http://hoser.lander.ca/SyndicationService.asmx/GetEntryCommentsRss?guid=c9cad210-3a70-4536-b94d-118d089a4062</wfw:commentRss>
      <body xmlns="http://www.w3.org/1999/xhtml">
        <p>
I finally decided that it was time to get a real network setup in my house. I had
some one-off network segments around the house for particular purposes, but not a
real whole-house network w/a set of primary interconnect points, in addition to CAT5e
drops around the house.
</p>
        <p>
This project really started this summer when we had the house painted. I ripped off
(imagine a violent action) all the coax and phone cords off the side of the house
prior to the painting, both to ensure that the paint got under the wires, and to remove
them permanently. I bought an <a href="http://www.silicondust.com/">HDHR</a> at the
same time to enable a new cable connection to my TV, over one of the network segments
that I mentioned earlier. That worked out nicely. Still, I wanted to be able to use
my HDHR on any PC in the house, and that's kinda difficult to reliably over 'g' wireless.
Others may argue the fact, but try viewing HD content, and you'll see that 'g' falls
on its face for that application, particularly if you have multiple streams going
at once. I could have gone 'n' and will, but I really wanted to get a gigE network
up and running, since it is fast and reliable.
</p>
        <p>
I also should note that my existing phone network had already proven to be pretty
bad. So, I already had an existing need to fix that.
</p>
        <p>
Off to Home Depot, which is pretty much the answer to all issues relating to the home.
Come back with 1000ft of riser CAT5e, 50 RJ45 connectors, a <a href="http://www.idealindustries.com/products/datacomm/tools/telemaster_telephone_tool.jsp">Ideal
crimper</a> and and <a href="http://www.idealindustries.com/prodDetail.do?prodId=62-200&amp;div=2&amp;l1=testers&amp;l2=testers_twisted_pair&amp;l3=62-200">Ideal
LinkMaster</a> CAT5 line tester. I also bought 8 large pieces of drywall, wood, some
insulation and a whole ton of other odds and sods, but that is indeed another project.
</p>
        <p>
I'm finding that cutting (to length) and crimping CAT5 is something of a challenge.
It is conceptually simple, but I appear to be still mastering this task. I've made
a bunch of mistakes, such as not following a wiring standard at first (even though
I've used them before for my earlier network segments), mistaking the pin order of
the connectors, and then incorrectly ordering the pins once I'd chosen T568A as the
standard to use. The test tool is kinda neat since it tells you exactly where and
how you've messed up. This is pretty useful if you've got a 50ft segment from your
basement to your attic that isn't able to create a connection.
</p>
        <p>
When I'm done, I'll have both a new phone network (over CAT5) and data network. The
phone network actually only uses 1/4 of a CAT5 line, but that's OK. The 'backbone'
is two CAT5 (one data, one phone) lines and one additional CAT5 line that I may need
later for some unknown reason. Every drop (phone or data) connects to this backbone
at one of three interconnect points (garage, attic and wiring closet in the basement).
This allows me to easily add machines, NAS, APs and pretty much any other kinda IP
appliance (like the HDHR) at any point in the network.
</p>
        <p>
My neighbor, who is in his 70s, keeps making references to me being able to "run Microsoft
on this network". It is pretty funny to hear that viewpoint. I'm sure that there is
more XBox Live traffic during the day on the internal MSFT network than my wee network
would ever be able to handle, except maybe on Christmas day ;)
</p>
        <img width="0" height="0" src="http://hoser.lander.ca/aggbug.ashx?id=c9cad210-3a70-4536-b94d-118d089a4062" />
      </body>
      <title>Wiring the house for CAT5e</title>
      <guid isPermaLink="false">http://hoser.lander.ca/PermaLink,guid,c9cad210-3a70-4536-b94d-118d089a4062.aspx</guid>
      <link>http://hoser.lander.ca/2007/12/04/WiringTheHouseForCAT5e.aspx</link>
      <pubDate>Tue, 04 Dec 2007 07:20:53 GMT</pubDate>
      <description>&lt;p&gt;
I finally decided that it was time to get a real network setup in my house. I had
some one-off network segments around the house for particular purposes, but not a
real whole-house network w/a set of primary interconnect points, in addition to CAT5e
drops around the house.
&lt;/p&gt;
&lt;p&gt;
This project really started this summer when we had the house painted. I ripped off
(imagine a violent action) all the coax and phone cords off the side of the house
prior to the painting, both to ensure that the paint got under the wires, and to remove
them permanently. I bought an &lt;a href="http://www.silicondust.com/"&gt;HDHR&lt;/a&gt; at the
same time to enable a new cable connection to my TV, over one of the network segments
that I mentioned earlier. That worked out nicely. Still, I wanted to be able to use
my HDHR on any PC in the house, and that's kinda difficult to reliably over 'g' wireless.
Others may argue the fact, but try viewing HD content, and you'll see that 'g' falls
on its face for that application, particularly if you have multiple streams going
at once. I could have gone 'n' and will, but I really wanted to get a gigE network
up and running, since it is fast and reliable.
&lt;/p&gt;
&lt;p&gt;
I also should note that my existing phone network had already proven to be pretty
bad. So, I already had an existing need to fix that.
&lt;/p&gt;
&lt;p&gt;
Off to Home Depot, which is pretty much the answer to all issues relating to the home.
Come back with 1000ft of riser CAT5e, 50 RJ45 connectors, a &lt;a href="http://www.idealindustries.com/products/datacomm/tools/telemaster_telephone_tool.jsp"&gt;Ideal
crimper&lt;/a&gt; and and &lt;a href="http://www.idealindustries.com/prodDetail.do?prodId=62-200&amp;amp;div=2&amp;amp;l1=testers&amp;amp;l2=testers_twisted_pair&amp;amp;l3=62-200"&gt;Ideal
LinkMaster&lt;/a&gt; CAT5 line tester. I also bought 8 large pieces of drywall, wood, some
insulation and a whole ton of other odds and sods, but that is indeed another project.
&lt;/p&gt;
&lt;p&gt;
I'm finding that cutting (to length) and crimping CAT5 is something of a challenge.
It is conceptually simple, but I appear to be still mastering this task. I've made
a bunch of mistakes, such as not following a wiring standard at first (even though
I've used them before for my earlier network segments), mistaking the pin order of
the connectors, and then incorrectly ordering the pins once I'd chosen T568A as the
standard to use. The test tool is kinda neat since it tells you exactly where and
how you've messed up. This is pretty useful if you've got a 50ft segment from your
basement to your attic that isn't able to create a connection.
&lt;/p&gt;
&lt;p&gt;
When I'm done, I'll have both a new phone network (over CAT5) and data network. The
phone network actually only uses 1/4 of a CAT5 line, but that's OK. The 'backbone'
is two CAT5 (one data, one phone) lines and one additional CAT5 line that I may need
later for some unknown reason. Every drop (phone or data) connects to this backbone
at one of three interconnect points (garage, attic and wiring closet in the basement).
This allows me to easily add machines, NAS, APs and pretty much any other kinda IP
appliance (like the HDHR) at any point in the network.
&lt;/p&gt;
&lt;p&gt;
My neighbor, who is in his 70s, keeps making references to me being able to "run Microsoft
on this network". It is pretty funny to hear that viewpoint. I'm sure that there is
more XBox Live traffic during the day on the internal MSFT network than my wee network
would ever be able to handle, except maybe on Christmas day ;)
&lt;/p&gt;
&lt;img width="0" height="0" src="http://hoser.lander.ca/aggbug.ashx?id=c9cad210-3a70-4536-b94d-118d089a4062" /&gt;</description>
      <comments>http://hoser.lander.ca/CommentView,guid,c9cad210-3a70-4536-b94d-118d089a4062.aspx</comments>
      <category>Networking</category>
    </item>
  </channel>
</rss>