<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Comments on: Replacing a Router with IPCop</title>
	<atom:link href="http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/</link>
	<description>Musings on technology and life</description>
	<pubDate>Tue, 06 Jan 2009 06:03:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darrin Chandler</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-208</link>
		<dc:creator>Darrin Chandler</dc:creator>
		<pubDate>Fri, 01 Jun 2007 16:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-208</guid>
		<description>"Use as intended" means clicking things in the web interface, pretty much.

There are people doing "under the hood" stuff with IPCop to do more complex setups than would be possible by clicking around the provided interface.

The advantages of IPCop in that situation are debatable. At that point you're dealing with the complexity of an outdated and customized Linux distro rather than a simple interface. Better to move to a "normal" distro then, or better yet OpenBSD.

And, yes, I think it'll do what you need. You've picked something (IPCop) that's designed for the task at hand. :)</description>
		<content:encoded><![CDATA[<p>&#8220;Use as intended&#8221; means clicking things in the web interface, pretty much.</p>
<p>There are people doing &#8220;under the hood&#8221; stuff with IPCop to do more complex setups than would be possible by clicking around the provided interface.</p>
<p>The advantages of IPCop in that situation are debatable. At that point you&#8217;re dealing with the complexity of an outdated and customized Linux distro rather than a simple interface. Better to move to a &#8220;normal&#8221; distro then, or better yet OpenBSD.</p>
<p>And, yes, I think it&#8217;ll do what you need. You&#8217;ve picked something (IPCop) that&#8217;s designed for the task at hand. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-207</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Fri, 01 Jun 2007 13:09:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-207</guid>
		<description>I'm not too sure what all "use it as intended" means, but I suspect I won't be pushing the limits.  A little DHCP, take advantage of the DNS cache, and probably some intrusion detection.  Nothing fancy.

Oh, and I did find a way to incorporate the LinkSys router into the setup:  it's my wireless access point.  One day if I get really ambitious I'll set up a BLUE interface.  For now, the router is hanging off the switch.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not too sure what all &#8220;use it as intended&#8221; means, but I suspect I won&#8217;t be pushing the limits.  A little DHCP, take advantage of the DNS cache, and probably some intrusion detection.  Nothing fancy.</p>
<p>Oh, and I did find a way to incorporate the LinkSys router into the setup:  it&#8217;s my wireless access point.  One day if I get really ambitious I&#8217;ll set up a BLUE interface.  For now, the router is hanging off the switch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mick Russell</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-206</link>
		<dc:creator>Mick Russell</dc:creator>
		<pubDate>Fri, 01 Jun 2007 06:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-206</guid>
		<description>I agree with Darrin - use IPCop for what it was intended and you can't go wrong.

I also use IPCops certificate based VPN capabilty to great effect - 4 sites linked 24/7 no problems.

The biggest problem I have encountered is people looking longingly at their old DSL/router and trying to incorporate it in their IPCop setup.</description>
		<content:encoded><![CDATA[<p>I agree with Darrin - use IPCop for what it was intended and you can&#8217;t go wrong.</p>
<p>I also use IPCops certificate based VPN capabilty to great effect - 4 sites linked 24/7 no problems.</p>
<p>The biggest problem I have encountered is people looking longingly at their old DSL/router and trying to incorporate it in their IPCop setup.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darrin Chandler</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-205</link>
		<dc:creator>Darrin Chandler</dc:creator>
		<pubDate>Thu, 31 May 2007 17:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-205</guid>
		<description>If a wrt54g could handle full bandwidth for days on end reliably, they would have gone even cheaper and slower. Those routers work &lt;strong&gt;great&lt;/strong&gt; for their intended use of affordable consumer service, but they aren't up to heavy loads over long periods. That's just engineering in action.

Personally, I like OpenBSD as a router platform. On that task, it's hard to beat. But since it's a general purpose OS you'd have to hike up a steeper learning curve to get your firewall in place.

There are a lot of people in the local LUG who use IPCop. It should serve you well. If you start getting too tricky you may have some issues, but using it the way it's meant to be used should be cake once you find your way around. This was almost certainly the best choice to get a capable firewall up without already knowing how to build one.</description>
		<content:encoded><![CDATA[<p>If a wrt54g could handle full bandwidth for days on end reliably, they would have gone even cheaper and slower. Those routers work <strong>great</strong> for their intended use of affordable consumer service, but they aren&#8217;t up to heavy loads over long periods. That&#8217;s just engineering in action.</p>
<p>Personally, I like OpenBSD as a router platform. On that task, it&#8217;s hard to beat. But since it&#8217;s a general purpose OS you&#8217;d have to hike up a steeper learning curve to get your firewall in place.</p>
<p>There are a lot of people in the local LUG who use IPCop. It should serve you well. If you start getting too tricky you may have some issues, but using it the way it&#8217;s meant to be used should be cake once you find your way around. This was almost certainly the best choice to get a capable firewall up without already knowing how to build one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-204</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Thu, 31 May 2007 12:17:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-204</guid>
		<description>No, not using Comcast.  RoadRunner here, provided through Time Warner Cable.  I've used lots of bandwidth before, and haven't had a problem.</description>
		<content:encoded><![CDATA[<p>No, not using Comcast.  RoadRunner here, provided through Time Warner Cable.  I&#8217;ve used lots of bandwidth before, and haven&#8217;t had a problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Harvey</title>
		<link>http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/comment-page-1/#comment-202</link>
		<dc:creator>Roy Harvey</dc:creator>
		<pubDate>Thu, 31 May 2007 11:17:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mischel.com/2007/05/30/replacing-a-router-with-ipcop/#comment-202</guid>
		<description>I hope you aren't getting your connection through Comcast.  See http://www.gripe2ed.com/scoop/story/2007/4/16/01320/7728 for why.</description>
		<content:encoded><![CDATA[<p>I hope you aren&#8217;t getting your connection through Comcast.  See <a href="http://www.gripe2ed.com/scoop/story/2007/4/16/01320/7728" rel="nofollow">http://www.gripe2ed.com/scoop/story/2007/4/16/01320/7728</a> for why.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
