I think packets need to be process switched for "debug ip packet" to see them. You need to "no ip route-cache" on the interfaces passing your interesting traffic. But BEWARE of doing this on a highly utilised interface and/or a device with high avg CPU utilisation. Also use a tightly targeted ACL e.g. "debug ip packet 199" so you don't kill the router. And/or stop debug msgs going to the console with "logging console info" as each msg to console causes CPU interupt so a debug flood will kill you.
debug ip packet can be extremely helpful but be VERY CAREFUL how you use it on a box you care about.
...and remember to turn on the "ip route-cache [cef]" interface configs again when finished (:
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...