![]() A few great resources I have used and/or reviewed are: As long as you can understand that protocol to a fairly deep level you can troubleshoot any RADIUS environment. One thing to keep in mind is that while every vendor of a dot1x solution (Cisco, Aruba, FreeRADIUS, Microsoft) has a certain way of going about authentication, they all fall back to the same protocol: 802.1X/RADIUS. …By taking advantage of the resources that are out there as well as practical labs. So the question is, how do we become masters of a protocol that is literally quite capable of being the success or demise of a network’s security and operation? I personally learned a lot about dot1x via trial and error through implementations in the past as well as lab time at home and during my CCIE studies. That being said a lot of times we as engineers get stuck in a state of understanding enough to be dangerous and not enough to be highly successful and more importantly, capable. This was a great idea, so please enjoy!Ĩ02.1X is typically the first step in one of the more advanced security implementations you will have to dip your toes into when moving your network to a secure state. ![]() He has graciously asked that I add a little more details including the packet captures so everyone can follow along. EDIT: After chatting with David Westcott I have made a few additions to this post. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |