<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>扶凯 &#187; 2.6.23</title>
	<atom:link href="http://www.php-oa.com/tag/2-6-23/feed" rel="self" type="application/rss+xml" />
	<link>http://www.php-oa.com</link>
	<description>执着的人，能把梦想，变成现实。</description>
	<lastBuildDate>Thu, 29 Jul 2010 08:07:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>iptables出错18446744073709551615和2.6.23以后使用connlimit的方法</title>
		<link>http://www.php-oa.com/2010/01/25/iptables-18446744073709551615-connlimit.html</link>
		<comments>http://www.php-oa.com/2010/01/25/iptables-18446744073709551615-connlimit.html#comments</comments>
		<pubDate>Mon, 25 Jan 2010 09:26:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[linux常用技巧]]></category>
		<category><![CDATA[18446744073709551615]]></category>
		<category><![CDATA[2.6.23]]></category>
		<category><![CDATA[connlimit]]></category>
		<category><![CDATA[Invalid argument]]></category>
		<category><![CDATA[iptables]]></category>

		<guid isPermaLink="false">http://www.php-oa.com/?p=2219</guid>
		<description><![CDATA[在2.6.23以上的内核中使用connlimit时,常常会出下面二个错 比如:当我们打 iptables -A INPUT -p tcp -s 192.168.1.10 -m connlimit --connlimit-above 3 -j DROP iptables: Unknown error 18446744073709551615 iptables:Invalid argument 在tail... ]]></description>
		<wfw:commentRss>http://www.php-oa.com/2010/01/25/iptables-18446744073709551615-connlimit.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->