This post refers to the process of how to implement the whole RADIUS server authentication lab via eNSP. Please see more information below.
A lot of you guys have asked that you want to explore the whole progress of the authentication via the RADIUS server, yet there are no real devices at hand.
So, in this post, I will introduce how to set up a lab on eNSP in order to implement this.
First of all, we need one or two virtual devices. I will use two virtual Windows devices in this lab.
One of the virtual windows runs the Windows Server 2012 and it works as the RADIUS server (we should configure the RADIUS service on the Windows Server 2012 first, which I will leave out in this post).
Another virtual Windows runs the Windows 7, which is considered as the client.
Then, configure the eNSP. Topology as per below:
The LSW1 switch works as the access device. Cloud2 connects to the authentication client, the virtual machine which runs Windows 7. Cloud1 connects the LSW1 and the RADIUS server virtual machine, which runs Windows server 2012.
The Cloud configuration as per below:
The Cloud should bind the two ports: one is the internal port, which is showed as the UDP BindingInfo, as the preceding picture shows. The other port should be the virtual NIC, which connected the Windows 7 or Windows server 2012.
After the whole connection has completed, the logical topology will be shown as per below:
The virtual NIC 1 and virtual NIC 2 are the two virtual NICs added in the VMware.
After the whole connection has completed, we can inspect the whole authetication progress and do the packet capture to inspect the detail progress.
