Skip to main content

dot1x with Cisco Switch in GNS3 and CentOS Client

Today, I successfully completed a lab in GNS3 to work with dot1x wired authentication. In my lab, I used Cisco IOU L2 Image, FreeRADIUS Servers for remote authentication and CentOS 7 as a Client operating system.

In this post I will show my working configuration for Cisco L2 Switch, where "no ip routing" is configured. And a snapshot for from CentOS for network security setting to authenticate with 802.1x protocol.

On switch I used following configurations
My Cisco IOU L2 Image is

ACCESS-SW#sh version | in  Version
Cisco IOS Software, Solaris Software (I86BI_LINUXL2-IPBASEK9-M), Experimental Version 15.1(20130726:213425) [dstivers-july26-2013-team_track 105]

!
ACCESS-SW#show run
!
! output only dot1x related configuration
!
aaa new-model
aaa group server radius RADIUS1
 server name FreeRADIUS
aaa authentication dot1x default group RADIUS1 local
dot1x system-auth-control
!
interface Ethernet3/0
 switchport access vlan 10
 switchport mode access
 authentication port-control auto
 dot1x pae authenticator
 spanning-tree portfast
end
!

To authenticate CentOS as a wired 802.1x client, see the below Snapshot for exact configuration


802.1x Configuration on CentOS

Comments

Popular posts from this blog

What is Cisco Supervisor Engine?

Supervisor Engine is a module that is installed in the Cisco Chassis-based Catalyst Switches or Routers. Supervisor engine contains nearly all the same components of a fixed Cisco Switches or Routers. These Supervisor engines come in a variety of different types with different functionalities and are installed in the Switches/Router Chassis as per requirements of the network types.

Benefits of Supervisor Engines
By installing Latest Supervisor Engines in your existing investments (Switches and Routers) you can scale system performance and integrate next-generation services into your Networks.
Within a single multilayer switch chassis, two supervisor modules with integrated route processors can be used to provide hardware redundancy. If an entire supervisor module fails, the other module can pick up the pieces and continue operating the switch.
The supervisor engine contains the following integrated daughter cards that perform forwarding and routing and provide the protocols supported …

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.