![]() ![]() Using a RADIUS server to authenticate clients, you can provide port-level security protection from unauthorized network access for the following authentication methods: ![]() (This is because a port can be an untagged member of only one VLAN at a time.) At the same time, if port “N” is already configured as an untagged member of another VLAN, port “N” loses access to that other VLAN for the duration of the session. When a client is authenticated on port “N”, if port “N” is not already configured as an untagged member of the static VLAN specified by the RADIUS server, then the switch temporarily assigns port “N” as an untagged member of the required VLAN (for the duration of the 802.1X session). If the port used by the client is not configured as an untagged member of the required static VLAN: If it is not, the switch temporarily reassigns the port as described below. Also, for the session to proceed, the port must be an untagged member of the required VLAN. If it does not exist or is a dynamic VLAN (created by GVRP), authentication fails. ![]() (Refer to the documentation provided with your RADIUS application.) The static VLAN to which a RADIUS server assigns a client must already exist on the switch. RADIUS authentication for an 802.1X client on a given port can include a (static) VLAN requirement. How RADIUS/802.1X authentication affects VLAN operation Static VLAN requirement:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |