<?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>Henry&#039;s Points &#187; Trouble Shooting</title>
	<atom:link href="http://henrydu.com/blog/category/networks/trouble-shooting/feed" rel="self" type="application/rss+xml" />
	<link>http://henrydu.com/blog</link>
	<description>Think analog, act digital</description>
	<lastBuildDate>Mon, 14 Nov 2011 18:32:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Getting Transit Packets on Router</title>
		<link>http://henrydu.com/blog/networks/getting-transit-packets-on-router-181.html</link>
		<comments>http://henrydu.com/blog/networks/getting-transit-packets-on-router-181.html#comments</comments>
		<pubDate>Tue, 19 May 2009 18:50:03 +0000</pubDate>
		<dc:creator>hengdu</dc:creator>
				<category><![CDATA[Networks]]></category>
		<category><![CDATA[Trouble Shooting]]></category>

		<guid isPermaLink="false">http://henrydu.com/blog/?p=181</guid>
		<description><![CDATA[If we use debug ip packet on Cisco router, we can only see the packets that originated on the router or destinated to the router. We cannot see any transit packets. The reason is, in the interface level, the command ip route-cache is enabled as default. We can define route-cache options to NetFlow or CEF. [...]]]></description>
			<content:encoded><![CDATA[<p>If we use <em><strong>debug ip packet</strong></em> on Cisco router, we can only see the packets that originated on the router or destinated to the router. We cannot see any transit packets. The reason is, in the interface level, the command <em><strong>ip route-cache</strong></em> is enabled as default. We can define route-cache options to NetFlow or CEF. On the most cases, route-cache is using CEF because <em><strong>ip cef</strong></em> is enabled on the global.</p>
<p>Therefore, we need to type <em><strong>no ip route-cache</strong></em> in interface level to let all transit IP packet to pass through processor.</p>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://henrydu.com/blog/networks/getting-transit-packets-on-router-181.html" target="_blank" title="Share on Facebook">Share on Facebook</a></p>]]></content:encoded>
			<wfw:commentRss>http://henrydu.com/blog/networks/getting-transit-packets-on-router-181.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

