![]() If you go back and enable all the protocols to be visible in the workspace by toggling the (show all/None) button in the simulation mode, you'd find a plenty of messages, most of which are STP messages, and you'd discover that your event list has really been saturated. ![]() So, the problem is actually not even a problem, rather than a misunderstanding of how the protocol filters work in PacketTracer's simulation mode. ![]() I'd post here to answer any future similar questions. ![]() Sorry to see that even after three years, this issue is still trending first in search engines without any single answer, and even in the newest version of (PacketTracer v7 atm), people are still facing this problem due to ambiguity.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |