<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Computing on Evan Hoffman</title><link>https://evan.wtf/tags/computing/</link><description>Recent content in Computing on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Thu, 09 Feb 2017 20:04:14 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/computing/index.xml" rel="self" type="application/rss+xml"/><item><title>Home NAS build, 2017 Edition</title><link>https://evan.wtf/2017/02/09/home-nas-build-2017-edition/</link><pubDate>Thu, 09 Feb 2017 20:04:14 +0000</pubDate><guid>https://evan.wtf/2017/02/09/home-nas-build-2017-edition/</guid><description>&lt;p&gt;Many years ago, before WiFi or even routers were common in homes, I was faced with the problem of how to connect multiple computers in my home to the internet when our cable provider only provided a single IP address. Being the late 1990s-early 2000s, this was a problem largely faced only by super-nerds like me, and the generally accepted solution was to build your own router, generally using a Linux box with two Ethernet ports, ipchains (or iptables, if you were bleeding-edge) to do NAT, DHCP and DNS. I had an old computer laying around so that’s what I did. This box served me well for many years, ultimately being replaced by a &lt;a href="https://en.wikipedia.org/wiki/Linksys_WRT54G_series#WRT54G"&gt;Linksys WRT54g&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>