We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 651 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

451 Sign Ups in the last 30 days

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags: , ,

Forum Replies

  1. Hi Rene,
    Which’s standard of RFC that I can follow when learning the TACACS+?
    Many thanks!

  2. Hello Thinh

    The original TACACS is defined in RFC 1492 as it is an open IETF standard. TACACS+ however was developed by Cisco so it has no corresponding RFC. Cisco developed it as an open standard so many vendors can and do use it.

    There is however a Cisco RFC TACACS+ Draft available on the IETF web site that you can check out. There are also additional drafts that have been added, the most recent of which can be found here.

    I hope this has been helpful!


  3. oh, thank you so much, i looked it out :slight_smile:

  4. Hello Markos

    Using port security we can do several things. We can restrict the use of a switch port to only one specific preconfigured MAC address or we can specify that only a single MAC address should be seen to be using this port. We can even use IP source guard to determine which will be the allowed source IP address that can use the interface, even on an L2 switch.

    The first case will allow us to lock the port down such that only a specific computer having a specific MAC address can connect to that port. If this were implemented, then port security woul

    ... Continue reading in our forum

  5. Hello Justin

    If I understood your argument correctly, you mean connect something like an access point or a SOHO router to the port-security enabled switchport and have that device perform NAT, where all hosts connected to that device will communicate on the network via the 802.1x enabled port using a single MAC and IP address, thus defeating port security, correct?

    Yes, this would “defeat” 802.1x if you had configured it to allow any single MAC address. However, you can configure it to allow only a particular MAC address, that of the only allowed workstation o

    ... Continue reading in our forum

10 more replies! Ask a question or join the discussion by visiting our Community Forum