<?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: How do I build a Simple Linux Firewall for DSL/Dial-up connection?</title> <atom:link href="http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html/feed" rel="self" type="application/rss+xml" /><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html</link> <description>This is a Linux sys admin journal by Vivek about sys admin work, Linux tips &#38; tricks, hacks, news and more.</description> <lastBuildDate>Fri, 10 Feb 2012 20:37:43 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Paul</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-149774</link> <dc:creator>Paul</dc:creator> <pubDate>Fri, 31 Jul 2009 05:53:04 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-149774</guid> <description>Standard practice with firewall rules, is to setup a default reject (fail safe) - and then an explicit reject rule. That way, if your rules don&#039;t load properly, things get dropped by default. And when you&#039;re looking over your rules - you can see your explicit reject, and not rely on the default (which is usually much earlier in the file, and not visible), just in case you forgot it, or it got changed on an upgrade or something silly like that...
It&#039;s about safety/security, which is what firewalls are for.</description> <content:encoded><![CDATA[<p>Standard practice with firewall rules, is to setup a default reject (fail safe) &#8211; and then an explicit reject rule. That way, if your rules don&#8217;t load properly, things get dropped by default. And when you&#8217;re looking over your rules &#8211; you can see your explicit reject, and not rely on the default (which is usually much earlier in the file, and not visible), just in case you forgot it, or it got changed on an upgrade or something silly like that&#8230;</p><p>It&#8217;s about safety/security, which is what firewalls are for.</p> ]]></content:encoded> </item> <item><title>By: Blingbling</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-143399</link> <dc:creator>Blingbling</dc:creator> <pubDate>Tue, 08 Apr 2008 07:40:50 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-143399</guid> <description>Why oh why do you first decide to drop all incoming packages that no other rule take care of (the policy) and then later on, just forget about this and set a &quot;reject&quot; for everything in step 4?</description> <content:encoded><![CDATA[<p>Why oh why do you first decide to drop all incoming packages that no other rule take care of (the policy) and then later on, just forget about this and set a &#8220;reject&#8221; for everything in step 4?</p> ]]></content:encoded> </item> <item><title>By: Chris</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-141634</link> <dc:creator>Chris</dc:creator> <pubDate>Tue, 06 Nov 2007 21:21:47 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-141634</guid> <description>Code in step 2 is incorrect:
iptables -A OUTPUT -i lo -j ACCEPT
cannot use -i with OUTPUT,
should read:
iptables -A OUTPUT -o lo -j ACCEPT</description> <content:encoded><![CDATA[<p>Code in step 2 is incorrect:<br
/> iptables -A OUTPUT -i lo -j ACCEPT</p><p>cannot use -i with OUTPUT,<br
/> should read:<br
/> iptables -A OUTPUT -o lo -j ACCEPT</p> ]]></content:encoded> </item> <item><title>By: ganesh</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19275</link> <dc:creator>ganesh</dc:creator> <pubDate>Wed, 16 Nov 2005 23:24:00 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19275</guid> <description>I must agree with LinuxTitli, with this samll script one can understand how linux firewall works. Good work, IMPO</description> <content:encoded><![CDATA[<p>I must agree with LinuxTitli, with this samll script one can understand how linux firewall works. Good work, IMPO</p> ]]></content:encoded> </item> <item><title>By: LinuxTitli</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19274</link> <dc:creator>LinuxTitli</dc:creator> <pubDate>Thu, 03 Nov 2005 09:58:00 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19274</guid> <description>Agreed. Howerver, they are only useful if you understand basis of iptables otherwise you can harm yourself more than the protecting yourself. And that is why you need to understand the iptables, once done it you can go for tools or ready to use scripts out there. Besides writing your own script saves more time in long run, IMPO.</description> <content:encoded><![CDATA[<p>Agreed. Howerver, they are only useful if you understand basis of iptables otherwise you can harm yourself more than the protecting yourself. And that is why you need to understand the iptables, once done it you can go for tools or ready to use scripts out there. Besides writing your own script saves more time in long run, IMPO.</p> ]]></content:encoded> </item> <item><title>By: Anonymous</title><link>http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19273</link> <dc:creator>Anonymous</dc:creator> <pubDate>Wed, 02 Nov 2005 21:49:00 +0000</pubDate> <guid
isPermaLink="false">http://www.cyberciti.biz/tips/how-do-i-build-a-simple-linux-firewall-for-dsldial-up-connection.html#comment-19273</guid> <description>There are many programs that automate the iptables process quite well and still allow for advanced rules. Check out &lt;a HREF=&quot;http://www.shorewall.net/&quot; rel=&quot;nofollow&quot;&gt;shorewall&lt;/A&gt;.</description> <content:encoded><![CDATA[<p>There are many programs that automate the iptables process quite well and still allow for advanced rules. Check out <a
HREF="http://www.shorewall.net/" rel="nofollow">shorewall</a>.</p> ]]></content:encoded> </item> </channel> </rss>
