<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Tech-Recipes - Latest Comments in How to (more) safely run debugs on Cisco routers | Cisco router | Tech-Recipes</title><link>http://tech-recipes.disqus.com/</link><description>Cookbook of Tech Tutorials</description><language>en</language><lastBuildDate>Thu, 09 Apr 2009 12:36:42 -0000</lastBuildDate><item><title>Re: How to (more) safely run debugs on Cisco routers | Cisco router | Tech-Recipes</title><link>http://www.tech-recipes.com/rx/1931/how_to_more_safely_run_debugs_on_cisco_routers/#comment-8009353</link><description>You are correct!  &lt;br&gt;&lt;br&gt;That was a typo on my part.  Great catch!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ahbanks</dc:creator><pubDate>Thu, 09 Apr 2009 12:36:42 -0000</pubDate></item><item><title>Re: How to (more) safely run debugs on Cisco routers | Cisco router | Tech-Recipes</title><link>http://www.tech-recipes.com/rx/1931/how_to_more_safely_run_debugs_on_cisco_routers/#comment-2770586</link><description>The last command in this example is incorrect as it doesn't use the access-list that's been defined. The last example should be:&lt;br&gt;&lt;br&gt;&lt;code&gt;&lt;br&gt;access-list 100 permit ip any host 1.1.1.1&lt;br&gt;access-list 100 permit ip host 1.1.1.1 any&lt;br&gt;&lt;br&gt;debug ip packet detail 100&lt;br&gt;&lt;/code&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;Note the &lt;em&gt;100&lt;/em&gt; at the end of the debug line. That applies ACL 100 to the debug. Without that you risk choking the router if it's at all busy.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AWfki</dc:creator><pubDate>Fri, 27 Jun 2008 07:12:48 -0000</pubDate></item></channel></rss>