<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/css" href="http://morison.biz/technotes/feeds/rss.css" ?>
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/" 
	xmlns:dc="http://purl.org/dc/elements/1.1/" 
	xmlns:icbm="http://postneo.com/icbm/" 
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/" 
	xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" 
	xmlns:wfw="http://wellformedweb.org/CommentAPI/" >

<channel>
	<title>Comments for: My Choice: Best IPTables Tutorial</title>
	<link>http://morison.biz/technotes/articles/57</link>
	<description>This link is hands down the best tutorial of IpTables I've come across.

Linux IpTables can be confounding. I usually create a rule and try it out with tcpdumps running on both sides, sort of a &quot;hail Mary&quot; approach. A careful read-through of Iptables Tutorial 1.2.2 really straightened me out. 

In particular, the DNAT Target section finally answered my questions, and fixed the issue, with my port forwarded servers not responding to clients from within their masqueraded network.

A very good read, especially if you've &quot;kinda&quot; figured out IpTables, just enough to be dangerous, but are missing some key points to get rules to do what you want.

(You can skip the lengthy SCTP coverage, unless that's something you're working with.)

Once again: http://iptables-tutorial.frozentux.net/iptables-tutorial.html</description>
	<language>en</language>
	<copyright>2006-2008, Rod Morison Software</copyright>
	<managingEditor>technotes@morison.biz</managingEditor>
	<lastBuildDate>Sun, 01 Aug 2010 10:28:46 GMT</lastBuildDate>
	<generator>Yet Another Community System</generator>
	<docs>http://blogs.law.harvard.edu/tech/rss</docs>
	<ttl>70</ttl>

</channel>
</rss>