<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>bradym.net &#187; Misc</title>
	<atom:link href="http://bradym.net/category/misc/feed" rel="self" type="application/rss+xml" />
	<link>http://bradym.net</link>
	<description>Random thoughts of a Code Monkey</description>
	<lastBuildDate>Sun, 11 Oct 2009 22:39:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Setting up Wireless with DSL</title>
		<link>http://bradym.net/misc/setting-up-wireless-with-dsl</link>
		<comments>http://bradym.net/misc/setting-up-wireless-with-dsl#comments</comments>
		<pubDate>Thu, 03 Jan 2008 03:19:54 +0000</pubDate>
		<dc:creator>bradym</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[Cisco 678]]></category>
		<category><![CDATA[DSL]]></category>
		<category><![CDATA[Linksys WRT54G]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://bradym.net/uncategorized/setting-up-wireless-with-dsl</guid>
		<description><![CDATA[It turns out that setting up wireless with DSL is a bit different than with cable modem, here&#8217;s how I got it to work.
In order to get it working I used a Cisco 678 DSL Modem, Linksys WRT54G Wireless Router and a Basic 5 port hub.
Here&#8217;s the process that I went through to get it [...]]]></description>
			<content:encoded><![CDATA[<p>It turns out that setting up wireless with DSL is a bit different than with cable modem, here&#8217;s how I got it to work.</p>
<p>In order to get it working I used a Cisco 678 DSL Modem, Linksys WRT54G Wireless Router and a Basic 5 port hub.</p>
<p>Here&#8217;s the process that I went through to get it working.</p>
<p><strong>Step 1: Configure Cisco 678</strong></p>
<p>The first thing I did was to enable the DHCP Server on the Cisco 678. Be sure to set the starting IP address and DNS servers on the Cisco, or it won&#8217;t work properly.</p>
<p>DSL Modem Setup:</p>
<p>IP Address: 192.168.1.1</p>
<p>Subnet Mask: 255.255.255.0</p>
<p>Starting IP Address: 192.168.1.100</p>
<p><strong>Step 2: Configure Linksys WRT54G</strong></p>
<p>Here&#8217;s the part that I had to call tech support for help with. The wireless router must be on a different subnet than the Cisco, or it will not work properly.</p>
<p>Wireless Router Setup:</p>
<p>IP Address: 192.168.2.1</p>
<p>Subnet Mask: 255.255.255.128</p>
<p>Starting IP Address: 192.168.2.100</p>
<p>The wireless router should be setup to get an IP address automatically, which is the default setting on the Linksys.</p>
<p>I also set the DNS servers on the Linksys to make sure that they would be set properly on client computers. It may work without this, but setting it here avoids possible problems.</p>
<p><strong>Step 3: Hook it all together</strong></p>
<p>Run a cable from the Cisco 678 to the uplink port in the hub. Then plug the wireless router into the hub as well, and you should be good to go.</p>
<p><strong>Additional Notes:</strong></p>
<ul>
<li>Computers plugged into the hub will be in the 192.168.1 subnet.</li>
<li>Computers plugged into the Linksys will be in the 192.168.2 subnet.</li>
</ul>
<p>If you plan to use your network for gaming or other network applications, it is important to have all of the computers on the same subnet. This would mean plugging any computers without wireless cards into the Linksys.</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fbradym.net%2Fmisc%2Fsetting-up-wireless-with-dsl';
  addthis_title  = 'Setting+up+Wireless+with+DSL';
  addthis_pub    = 'mydarb';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://bradym.net/misc/setting-up-wireless-with-dsl/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Choosing a Domain Registrar</title>
		<link>http://bradym.net/misc/choosing-a-domain-registrar</link>
		<comments>http://bradym.net/misc/choosing-a-domain-registrar#comments</comments>
		<pubDate>Thu, 03 Jan 2008 03:17:54 +0000</pubDate>
		<dc:creator>bradym</dc:creator>
				<category><![CDATA[Misc]]></category>
		<category><![CDATA[Domain]]></category>
		<category><![CDATA[Registrar]]></category>

		<guid isPermaLink="false">http://bradym.net/misc/choosing-a-domain-registrar</guid>
		<description><![CDATA[At one point between work and personal sites, I managed close to 10 different domain names. A couple years ago I decided it was time move all of the domain names I manage to one account to make my life easier.
Two of the domains I had registered before this time were with Namesecure, and it [...]]]></description>
			<content:encoded><![CDATA[<p>At one point between work and personal sites, I managed close to 10 different domain names. A couple years ago I decided it was time move all of the domain names I manage to one account to make my life easier.</p>
<p>Two of the domains I had registered before this time were with Namesecure, and it quickly became apparent that choosing them was a mistake.</p>
<p>One domain was transferred without problems, but getting the other domain transferred took nearly a year. Through the process of getting this domain transferred, I learned two very important lessons.</p>
<p><strong>Never do business with a company that doesn&#8217;t provide phone support</strong></p>
<p>When I originally registered my domain names I didn&#8217;t care that Namesecure didn&#8217;t have phone support because I figured I could take care of most things myself, and e-mail is easier to deal with anyways.</p>
<p>But when a problem came along, I learned the value of phone support. Had I been able to call at the first sign of a problem and speak with someone in a support department it would have probably been resolved within a week or so.</p>
<p><strong>Make sure the registrar offers all of the services you want</strong></p>
<p>Is it important to you to be able to manage your DNS entries yourself? Do you need e-mail forwarding? Will you need to change/add subdomains on a frequent basis or on a whim?</p>
<p>Make sure the company you choose will allow you to do what you need to do! Had I originally chosen a company that provided all of the features I now want to use I wouldn&#8217;t have had to transfer my domains in the first place.</p>
<p><strong>My recommendation</strong></p>
<p>I highly recommend <a href="http://domainsite.com" target="_blank">Domainsite</a> as a registrar. They give you complete access to your domain name and DNS entries though their website that works well and is easy to use. They also have very good prices for domain name registration.</p>
<p>When you have a problem or question, they have great support. <a href="http://domainsite.com" target="_blank">Domainsite</a> has their mailing address, phone number, and support e-mail address right on the top of every page on their website.</p>
<p>Just a note: I am not an employee of <a href="http://domainsite.com" target="_blank">Domainsite</a>, just a satisfied customer.</p>
<script type="text/javascript">
  addthis_url    = 'http%3A%2F%2Fbradym.net%2Fmisc%2Fchoosing-a-domain-registrar';
  addthis_title  = 'Choosing+a+Domain+Registrar';
  addthis_pub    = 'mydarb';
</script><script type="text/javascript" src="http://s7.addthis.com/js/addthis_widget.php?v=12" ></script>
]]></content:encoded>
			<wfw:commentRss>http://bradym.net/misc/choosing-a-domain-registrar/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
