<?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: iptables for Asterisk and FreePBX</title>
	<atom:link href="http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772/feed" rel="self" type="application/rss+xml" />
	<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772</link>
	<description>UK based Asterisk, Trixbox, FreePBX and A2Billing Servers</description>
	<lastBuildDate>Mon, 06 Feb 2012 16:56:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Dan</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-2362</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Sun, 09 Jan 2011 21:09:36 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-2362</guid>
		<description>iptables --list 

returns:

[root@localhost ~]# iptables --list
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       all  -f  anywhere             anywhere
DROP       tcp  --  anywhere             anywhere            tcp flags:!FIN,SYN,RST,ACK/SYN state NEW
DROP       all  -f  anywhere             anywhere
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST                                                   ,PSH,ACK,URG
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE
ACCEPT     all  --  anywhere             anywhere
ACCEPT     all  --  anywhere             anywhere            state RELATED,ESTABLISHED
DROP       tcp  --  anywhere             anywhere            tcp flags:!FIN,SYN,RST,ACK/SYN state NEW
DROP       all  -f  anywhere             anywhere
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST                                                   ,PSH,ACK,URG
DROP       tcp  --  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:upnotifyp
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:ssh state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:https state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:http state NEW
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:sip
ACCEPT     udp  --  anywhere             anywhere            udp dpt:sip
ACCEPT     udp  --  anywhere             anywhere            udp dpts:ndmp:dnp
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:sip-tls
ACCEPT     udp  --  anywhere             anywhere            udp dpt:sip-tls
ACCEPT     udp  --  anywhere             anywhere            udp dpt:iax
ACCEPT     icmp --  anywhere             anywhere            icmp echo-request state NEW
REJECT     all  --  anywhere             anywhere            reject-with icmp-port-unreachable

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


Would that indicate i have setup iptables correctly?</description>
		<content:encoded><![CDATA[<p>iptables &#8211;list </p>
<p>returns:</p>
<p>[root@localhost ~]# iptables &#8211;list<br />
Chain INPUT (policy ACCEPT)<br />
target     prot opt source               destination<br />
DROP       all  -f  anywhere             anywhere<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:!FIN,SYN,RST,ACK/SYN state NEW<br />
DROP       all  -f  anywhere             anywhere<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST                                                   ,PSH,ACK,URG<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE<br />
ACCEPT     all  &#8212;  anywhere             anywhere<br />
ACCEPT     all  &#8212;  anywhere             anywhere            state RELATED,ESTABLISHED<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:!FIN,SYN,RST,ACK/SYN state NEW<br />
DROP       all  -f  anywhere             anywhere<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST                                                   ,PSH,ACK,URG<br />
DROP       tcp  &#8212;  anywhere             anywhere            tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:upnotifyp<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:ssh state NEW<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:https state NEW<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:http state NEW<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:sip<br />
ACCEPT     udp  &#8212;  anywhere             anywhere            udp dpt:sip<br />
ACCEPT     udp  &#8212;  anywhere             anywhere            udp dpts:ndmp:dnp<br />
ACCEPT     tcp  &#8212;  anywhere             anywhere            tcp dpt:sip-tls<br />
ACCEPT     udp  &#8212;  anywhere             anywhere            udp dpt:sip-tls<br />
ACCEPT     udp  &#8212;  anywhere             anywhere            udp dpt:iax<br />
ACCEPT     icmp &#8212;  anywhere             anywhere            icmp echo-request state NEW<br />
REJECT     all  &#8212;  anywhere             anywhere            reject-with icmp-port-unreachable</p>
<p>Chain FORWARD (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Chain OUTPUT (policy ACCEPT)<br />
target     prot opt source               destination</p>
<p>Would that indicate i have setup iptables correctly?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1503</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Sat, 06 Feb 2010 18:03:46 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1503</guid>
		<description>Good tip. Thanks. Webmin is great and very easy to install.

You&#039;ll need to open TCP port 10000 (the default) to be able to access the Webmin interface.</description>
		<content:encoded><![CDATA[<p>Good tip. Thanks. Webmin is great and very easy to install.</p>
<p>You&#8217;ll need to open TCP port 10000 (the default) to be able to access the Webmin interface.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VortexRotor</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1502</link>
		<dc:creator>VortexRotor</dc:creator>
		<pubDate>Sat, 06 Feb 2010 17:57:50 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1502</guid>
		<description>Great little How-To.  I have been using Linux, IPtables, and Elastix for years and have also utilized a config as above.

I would recommend for anyone whether your a veteran of everything *NIX or not and especially if your a novice to install and use webmin as it makes day-to-day management extremely simply and straight forward especially for IPTables config.</description>
		<content:encoded><![CDATA[<p>Great little How-To.  I have been using Linux, IPtables, and Elastix for years and have also utilized a config as above.</p>
<p>I would recommend for anyone whether your a veteran of everything *NIX or not and especially if your a novice to install and use webmin as it makes day-to-day management extremely simply and straight forward especially for IPTables config.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1441</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Mon, 09 Nov 2009 19:21:39 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1441</guid>
		<description>Hi Henry,

It&#039;s true that the numbers in the brackets are packet/byte counts for the rules. Editing the iptables file directly is not the &#039;correct&#039; way to setup iptables (really it&#039;s better to use the iptables command) but it&#039;s a quick and easy hack. 

If you&#039;re not doing any ip traffic accounting using iptables then you can just ignore the numbers. If you are then it&#039;s probably best not to edit the iptables file in this way.</description>
		<content:encoded><![CDATA[<p>Hi Henry,</p>
<p>It&#8217;s true that the numbers in the brackets are packet/byte counts for the rules. Editing the iptables file directly is not the &#8216;correct&#8217; way to setup iptables (really it&#8217;s better to use the iptables command) but it&#8217;s a quick and easy hack. </p>
<p>If you&#8217;re not doing any ip traffic accounting using iptables then you can just ignore the numbers. If you are then it&#8217;s probably best not to edit the iptables file in this way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1440</link>
		<dc:creator>Henry</dc:creator>
		<pubDate>Mon, 09 Nov 2009 04:01:37 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1440</guid>
		<description>Hi, I don&#039;t have a lot of experience with iptables but I think I understand the script very well. I just don&#039;t understand where the numbers between the [] come from like :OUTPUT ACCEPT [46823:2584014].  I have read a lot of iptables tutorials to see if I can find the answer myself but I have not been able to. The only thing I found is that they are packet count and byte count. Would you mind explaining it?</description>
		<content:encoded><![CDATA[<p>Hi, I don&#8217;t have a lot of experience with iptables but I think I understand the script very well. I just don&#8217;t understand where the numbers between the [] come from like :OUTPUT ACCEPT [46823:2584014].  I have read a lot of iptables tutorials to see if I can find the answer myself but I have not been able to. The only thing I found is that they are packet count and byte count. Would you mind explaining it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1343</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Thu, 06 Aug 2009 16:13:27 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1343</guid>
		<description>Are you sure? I don&#039;t think so. It&#039;s just redirecting the rules back out to the iptables service config file. No real need to do that bit really I guess as you just updated the file directly anyway.</description>
		<content:encoded><![CDATA[<p>Are you sure? I don&#8217;t think so. It&#8217;s just redirecting the rules back out to the iptables service config file. No real need to do that bit really I guess as you just updated the file directly anyway.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: areski</title>
		<link>http://sysadminman.net/blog/2009/iptables-for-asterisk-and-freepbx-772#comment-1342</link>
		<dc:creator>areski</dc:creator>
		<pubDate>Thu, 06 Aug 2009 16:01:54 +0000</pubDate>
		<guid isPermaLink="false">http://sysadminman.net/blog/?p=772#comment-1342</guid>
		<description>error on :
iptables-save &gt; /etc/sysconfig/iptables

should be :
iptables-save &lt; /etc/sysconfig/iptables</description>
		<content:encoded><![CDATA[<p>error on :<br />
iptables-save &gt; /etc/sysconfig/iptables</p>
<p>should be :<br />
iptables-save &lt; /etc/sysconfig/iptables</p>
]]></content:encoded>
	</item>
</channel>
</rss>

