• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 253
  • Last Modified:

Multi-Domain Authentication

i am trying to authenticate telephone and PC trhough a Multi-Domain enabled switchport. The telephone uses MAB to gain access to the domain and it does so successfully. when i connect the PC directly on the dot1x switchport it does not gain access to the domain. once i turn the implementation of the switchport to multi-host the PC authenticates with Dot1x successfully!

my switchport setup is as follows:
Current configuration : 545 bytes
!
interface GigabitEthernet1/0/19
 description Dot1x KM office test link
 switchport mode access
 switchport voice vlan 100
 no logging event link-status
 shutdown
 authentication event fail action next-method
 authentication event server dead action authorize vlan 300
 authentication event no-response action authorize vlan 1023
 authentication host-mode multi-domain
 authentication port-control auto
 mab
 dot1x pae authenticator
 storm-control broadcast level 0.50 0.40
 storm-control multicast level 0.50 0.40
 spanning-tree portfast
end
0
Christoforos Acadjiotis
Asked:
Christoforos Acadjiotis
  • 11
  • 9
1 Solution
 
Craig BeckCommented:
So you connect the PC straight to the switch and it doesn't work using multi domain?

Can you debug the dot1x authentication at the switch and post the output?
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
Hi and thanks a lot for the reply! This is the debug i get:

Mar 29 2015 12:18:24.039 EET: dot1x-ev(Gi1/0/19): Interface state changed to UP
Mar 29 2015 12:18:24.044 EET:     dot1x_auth Gi1/0/19: initial state auth_initialize has enter
Mar 29 2015 12:18:24.044 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_initialize_enter called
Mar 29 2015 12:18:24.044 EET:     dot1x_auth Gi1/0/19: during state auth_initialize, got event 0(cfg_auto)
Mar 29 2015 12:18:24.044 EET: @@@ dot1x_auth Gi1/0/19: auth_initialize -> auth_disconnected
Mar 29 2015 12:18:24.044 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_disconnected_enter called
Mar 29 2015 12:18:24.044 EET:     dot1x_auth Gi1/0/19: idle during state auth_disconnected
Mar 29 2015 12:18:24.044 EET: @@@ dot1x_auth Gi1/0/19: auth_disconnected -> auth_restart
Mar 29 2015 12:18:24.044 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_enter called
Mar 29 2015 12:18:24.044 EET: dot1x-ev(Gi1/0/19): Sending create new context event to EAP for 0xF0000090 (0000.0000.0000)
Mar 29 2015 12:18:24.044 EET:     dot1x_auth_bend Gi1/0/19: initial state auth_bend_initialize has enter
Mar 29 2015 12:18:24.044 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_initialize_enter called
Mar 29 2015 12:18:24.044 EET:     dot1x_auth_bend Gi1/0/19: initial state auth_bend_initialize has idle
Mar 29 2015 12:18:24.044 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_initialize, got event 16383(idle)
Mar 29 2015 12:18:24.049 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_initialize -> auth_bend_idle
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_enter called
Mar 29 2015 12:18:24.049 EET: dot1x-ev(Gi1/0/19): Created a client entry (0xF0000090)
Mar 29 2015 12:18:24.049 EET: dot1x-ev(Gi1/0/19): Dot1x authentication started for 0xF0000090 (0000.0000.0000)
Mar 29 2015 12:18:24.049 EET: dot1x-ev:DOT1X Supplicant not enabled on GigabitEthernet1/0/19
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): Posting !EAP_RESTART on Client 0xF0000090
Mar 29 2015 12:18:24.049 EET:     dot1x_auth Gi1/0/19: during state auth_restart, got event 6(no_eapRestart)
Mar 29 2015 12:18:24.049 EET: @@@ dot1x_auth Gi1/0/19: auth_restart -> auth_connecting
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_enter called
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_connecting_action called
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): Posting RX_REQ on Client 0xF0000090
Mar 29 2015 12:18:24.049 EET:     dot1x_auth Gi1/0/19: during state auth_connecting, got event 10(eapReq_no_reAuthMax)
Mar 29 2015 12:18:24.049 EET: @@@ dot1x_auth Gi1/0/19: auth_connecting -> auth_authenticating
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_enter called
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_authenticating_action called
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): Posting AUTH_START for 0xF0000090
Mar 29 2015 12:18:24.049 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_idle, got event 4(eapReq_authStart)
Mar 29 2015 12:18:24.049 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_idle -> auth_bend_request
Mar 29 2015 12:18:24.049 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.049 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to group PAE address
Mar 29 2015 12:18:24.049 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.049 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.049 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.049 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.049 EET: EAPOL Version: 0x3  type: 0x0  length: 0x0005
Mar 29 2015 12:18:24.049 EET: EAP code: 0x1  id: 0x1  length: 0x0005 type: 0x1 
Mar 29 2015 12:18:24.049 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0000.0000.0000)
Mar 29 2015 12:18:24.054 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_request_action called
Mar 29 2015 12:18:24.159 EET: dot1x-ev(Gi1/0/19): New client notification from AuthMgr for 0xF0000090 - 0050.b67c.0c14
Mar 29 2015 12:18:24.159 EET: %AUTHMGR-5-START: Starting 'dot1x' for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): Posting RESTART on Client 0xF0000090
Mar 29 2015 12:18:24.159 EET:     dot1x_auth Gi1/0/19: during state auth_authenticating, got event 13(restart)
Mar 29 2015 12:18:24.159 EET: @@@ dot1x_auth Gi1/0/19: auth_authenticating -> auth_aborting
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_exit called
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_enter called
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_aborting_action called
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): Posting AUTH_ABORT for 0xF0000090
Mar 29 2015 12:18:24.159 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 1(authAbort)
Mar 29 2015 12:18:24.159 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_initialize
Mar 29 2015 12:18:24.159 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_initialize_enter called
Mar 29 2015 12:18:24.165 EET:     dot1x_auth_bend Gi1/0/19: idle during state auth_bend_initialize
Mar 29 2015 12:18:24.165 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_initialize -> auth_bend_idle
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_enter called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): Posting !AUTH_ABORT on Client 0xF0000090
Mar 29 2015 12:18:24.165 EET:     dot1x_auth Gi1/0/19: during state auth_aborting, got event 20(no_eapolLogoff_no_authAbort)
Mar 29 2015 12:18:24.165 EET: @@@ dot1x_auth Gi1/0/19: auth_aborting -> auth_restart
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_exit called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_enter called
Mar 29 2015 12:18:24.165 EET: dot1x-ev(Gi1/0/19): Resetting the client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.165 EET: dot1x-ev(Gi1/0/19): Sending create new context event to EAP for 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_restart_action called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): Posting !EAP_RESTART on Client 0xF0000090
Mar 29 2015 12:18:24.165 EET:     dot1x_auth Gi1/0/19: during state auth_restart, got event 6(no_eapRestart)
Mar 29 2015 12:18:24.165 EET: @@@ dot1x_auth Gi1/0/19: auth_restart -> auth_connecting
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_enter called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_connecting_action called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): Posting RX_REQ on Client 0xF0000090
Mar 29 2015 12:18:24.165 EET:     dot1x_auth Gi1/0/19: during state auth_connecting, got event 10(eapReq_no_reAuthMax)
Mar 29 2015 12:18:24.165 EET: @@@ dot1x_auth Gi1/0/19: auth_connecting -> auth_authenticating
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_enter called
Mar 29 2015 12:18:24.165 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_authenticating_action called
Mar 29 2015 12:18:24.170 EET: dot1x-sm(Gi1/0/19): Posting AUTH_START for 0xF0000090
Mar 29 2015 12:18:24.170 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_idle, got event 4(eapReq_authStart)
Mar 29 2015 12:18:24.170 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_idle -> auth_bend_request
Mar 29 2015 12:18:24.170 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.170 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:24.170 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.170 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.170 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.170 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.170 EET: EAPOL Version: 0x3  type: 0x0  length: 0x0005
Mar 29 2015 12:18:24.170 EET: EAP code: 0x1  id: 0x1  length: 0x0005 type: 0x1 
Mar 29 2015 12:18:24.170 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.170 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_request_action called
Mar 29 2015 12:18:24.201 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.201 EET: dot1x-packet(Gi1/0/19): queuing an EAPOL pkt on Auth Q
Mar 29 2015 12:18:24.201 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:24.201 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.201 EET: EAPOL Version: 0x1  type: 0x1  length: 0x0000
Mar 29 2015 12:18:24.201 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 0,TYPE= 0,LEN= 0

Mar 29 2015 12:18:24.201 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:24.201 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0101.0000
Mar 29 2015 12:18:24.201 EET: dot1x-packet(Gi1/0/19): Received an EAPOL-Start packet
Mar 29 2015 12:18:24.201 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.201 EET: EAPOL Version: 0x1  type: 0x1  length: 0x0000
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_START on Client 0xF0000090
Mar 29 2015 12:18:24.201 EET:     dot1x_auth Gi1/0/19: during state auth_authenticating, got event 4(eapolStart)
Mar 29 2015 12:18:24.201 EET: @@@ dot1x_auth Gi1/0/19: auth_authenticating -> auth_aborting
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_exit called
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_enter called
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): Posting AUTH_ABORT for 0xF0000090
Mar 29 2015 12:18:24.201 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 1(authAbort)
Mar 29 2015 12:18:24.201 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_initialize
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_initialize_enter called
Mar 29 2015 12:18:24.201 EET:     dot1x_auth_bend Gi1/0/19: idle during state auth_bend_initialize
Mar 29 2015 12:18:24.201 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_initialize -> auth_bend_idle
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_enter called
Mar 29 2015 12:18:24.201 EET: dot1x-sm(Gi1/0/19): Posting !AUTH_ABORT on Client 0xF0000090
Mar 29 2015 12:18:24.206 EET:     dot1x_auth Gi1/0/19: during state auth_aborting, got event 20(no_eapolLogoff_no_authAbort)
Mar 29 2015 12:18:24.206 EET: @@@ dot1x_auth Gi1/0/19: auth_aborting -> auth_restart
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_exit called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_enter called
Mar 29 2015 12:18:24.206 EET: dot1x-ev(Gi1/0/19): Resetting the client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.206 EET: dot1x-ev(Gi1/0/19): Sending create new context event to EAP for 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_aborting_restart_action called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): Posting !EAP_RESTART on Client 0xF0000090
Mar 29 2015 12:18:24.206 EET:     dot1x_auth Gi1/0/19: during state auth_restart, got event 6(no_eapRestart)
Mar 29 2015 12:18:24.206 EET: @@@ dot1x_auth Gi1/0/19: auth_restart -> auth_connecting
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_enter called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_restart_connecting_action called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): Posting RX_REQ on Client 0xF0000090
Mar 29 2015 12:18:24.206 EET:     dot1x_auth Gi1/0/19: during state auth_connecting, got event 10(eapReq_no_reAuthMax)
Mar 29 2015 12:18:24.206 EET: @@@ dot1x_auth Gi1/0/19: auth_connecting -> auth_authenticating
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_enter called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_connecting_authenticating_action called
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): Posting AUTH_START for 0xF0000090
Mar 29 2015 12:18:24.206 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_idle, got event 4(eapReq_authStart)
Mar 29 2015 12:18:24.206 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_idle -> auth_bend_request
Mar 29 2015 12:18:24.206 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.206 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:24.206 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.206 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.206 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.206 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.206 EET: EAPOL Version: 0x3  type: 0x0  length: 0x0005
Mar 29 2015 12:18:24.212 EET: EAP code: 0x1  id: 0x1  length: 0x0005 type: 0x1 
Mar 29 2015 12:18:24.212 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.212 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_request_action called
Mar 29 2015 12:18:24.238 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.238 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:24.238 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:24.238 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.238 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0016
Mar 29 2015 12:18:24.238 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 1,LEN= 22

Mar 29 2015 12:18:24.238 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:24.238 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.0016
Mar 29 2015 12:18:24.238 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:24.238 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.238 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0016
Mar 29 2015 12:18:24.238 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:24.238 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:24.238 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:24.238 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:24.238 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:24.238 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.238 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:24.248 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:24.248 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:24.248 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:24.248 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:24.248 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.248 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:24.248 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.248 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.248 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.248 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.248 EET: EAPOL Version: 0x3  type: 0x0  length: 0x0006
Mar 29 2015 12:18:24.248 EET: EAP code: 0x1  id: 0x2  length: 0x0006 type: 0x19
Mar 29 2015 12:18:24.248 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.248 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:24.254 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.254 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:24.254 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:24.254 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.254 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0096
Mar 29 2015 12:18:24.254 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 150

Mar 29 2015 12:18:24.254 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:24.254 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.0096
Mar 29 2015 12:18:24.254 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:24.254 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.254 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0096
Mar 29 2015 12:18:24.254 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:24.259 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:24.259 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:24.259 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:24.259 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:24.259 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.259 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:24.264 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:24.264 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:24.264 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:24.264 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:24.264 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.264 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:24.264 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.264 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.264 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.264 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.264 EET: EAPOL Version: 0x3  type: 0x0  length: 0x009B
Mar 29 2015 12:18:24.264 EET: EAP code: 0x1  id: 0x3  length: 0x009B type: 0x19
Mar 29 2015 12:18:24.264 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.264 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:24.280 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.280 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:24.280 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:24.280 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.280 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0045
Mar 29 2015 12:18:24.280 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 69

Mar 29 2015 12:18:24.280 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:24.280 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.0045
Mar 29 2015 12:18:24.280 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:24.280 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.280 EET: EAPOL Version: 0x1  type: 0x0  length: 0x0045
Mar 29 2015 12:18:24.280 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:24.280 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:24.280 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:24.280 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:24.280 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:24.280 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.280 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:24.285 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:24.285 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:24.285 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:24.285 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:24.285 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:24.290 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:24.290 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.290 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:24.290 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:24.290 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:24.290 EET: EAPOL Version: 0x3  type: 0x0  length: 0x006B
Mar 29 2015 12:18:24.290 EET: EAP code: 0x1  id: 0x6  length: 0x006B type: 0x19
Mar 29 2015 12:18:24.290 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.290 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:24.290 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:24.290 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:24.290 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:24.290 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.290 EET: EAPOL Version: 0x1  type: 0x0  length: 0x002B
Mar 29 2015 12:18:24.290 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 43

Mar 29 2015 12:18:24.290 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:24.290 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.002b
Mar 29 2015 12:18:24.290 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:24.290 EET: EAPOL pak dump rx
Mar 29 2015 12:18:24.290 EET: EAPOL Version: 0x1  type: 0x0  length: 0x002B
Mar 29 2015 12:18:24.290 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:24.296 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:24.296 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:24.296 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:24.296 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:24.296 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:24.296 EET: dot1x-sm(Gi1/0/19): 
cy1-b2-c2960-7(config-if)#0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:25.014 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:25.014 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:25.014 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:25.014 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:25.014 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:25.014 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:25.014 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:25.014 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:25.014 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:25.014 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:25.014 EET: EAPOL Version: 0x3  type: 0x0  length: 0x002B
Mar 29 2015 12:18:25.014 EET: EAP code: 0x1  id: 0x7  length: 0x002B type: 0x19
Mar 29 2015 12:18:25.014 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:25.014 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:25.066 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:25.066 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:25.066 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:25.066 EET: EAPOL pak dump rx
Mar 29 2015 12:18:25.066 EET: EAPOL Version: 0x1  type: 0x0  length: 0x003B
Mar 29 2015 12:18:25.066 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 59

Mar 29 2015 12:18:25.066 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:25.066 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.003b
Mar 29 2015 12:18:25.066 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:25.066 EET: EAPOL pak dump rx
Mar 29 2015 12:18:25.066 EET: EAPOL Version: 0x1  type: 0x0  length: 0x003B
Mar 29 2015 12:18:25.066 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:25.066 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:25.066 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:25.066 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:25.066 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:25.066 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:25.066 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:25.140 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:25.140 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:25.140 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:25.140 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:25.140 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:25.145 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:25.145 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:25.145 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:25.145 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:25.145 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:25.145 EET: EAPOL Version: 0x3  type: 0x0  length: 0x003B
Mar 29 2015 12:18:25.145 EET: EAP code: 0x1  id: 0x8  length: 0x003B type: 0x19
Mar 29 2015 12:18:25.145 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:25.145 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:25.402 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:25.402 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:25.402 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:25.412 EET: EAPOL pak dump rx
Mar 29 2015 12:18:25.412 EET: EAPOL Version: 0x1  type: 0x0  length: 0x003B
Mar 29 2015 12:18:25.412 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 59

Mar 29 2015 12:18:25.412 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:25.412 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.003b
Mar 29 2015 12:18:25.412 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:25.412 EET: EAPOL pak dump rx
Mar 29 2015 12:18:25.412 EET: EAPOL Version: 0x1  type: 0x0  length: 0x003B
Mar 29 2015 12:18:25.412 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:25.418 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090

Mar 29 2015 12:18:25.418 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:25.423 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:25.423 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:25.423 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:25.423 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:26.283 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:26.283 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:26.283 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:26.283 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:26.288 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:26.288 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:26.288 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:26.288 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:26.288 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:26.288 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:26.288 EET: EAPOL Version: 0x3  type: 0x0  length: 0x004B
Mar 29 2015 12:18:26.288 EET: EAP code: 0x1  id: 0x9  length: 0x004B type: 0x19
Mar 29 2015 12:18:26.288 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:26.288 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:26.330 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:26.330 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:26.330 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:26.330 EET: EAPOL pak dump rx
Mar 29 2015 12:18:26.330 EET: EAPOL Version: 0x1  type: 0x0  length: 0x006B
Mar 29 2015 12:18:26.330 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 107

Mar 29 2015 12:18:26.330 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:26.330 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.006b
Mar 29 2015 12:18:26.330 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:26.330 EET: EAPOL pak dump rx
Mar 29 2015 12:18:26.330 EET: EAPOL Version: 0x1  type: 0x0  length: 0x006B
Mar 29 2015 12:18:26.330 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:26.330 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:26.330 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:26.330 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:26.330 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:26.330 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:26.330 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:27.012 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:27.012 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:27.012 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:27.012 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:27.012 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:27.012 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:27.012 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:27.012 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:27.012 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:27.012 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:27.012 EET: EAPOL Version: 0x3  type: 0x0  length: 0x005B
Mar 29 2015 12:18:27.012 EET: EAP code: 0x1  id: 0xA  length: 0x005B type: 0x19
Mar 29 2015 12:18:27.012 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:27.012 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:27.038 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:27.038 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:27.038 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:27.038 EET: EAPOL pak dump rx
Mar 29 2015 12:18:27.038 EET: EAPOL Version: 0x1  type: 0x0  length: 0x002B
Mar 29 2015 12:18:27.038 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 43

Mar 29 2015 12:18:27.038 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:27.038 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.002b
Mar 29 2015 12:18:27.038 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:27.038 EET: EAPOL pak dump rx
Mar 29 2015 12:18:27.038 EET: EAPOL Version: 0x1  type: 0x0  length: 0x002B
Mar 29 2015 12:18:27.038 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:27.038 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:27.038 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)

Mar 29 2015 12:18:27.038 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:27.038 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:27.038 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:27.038 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:27.861 EET: dot1x-sm(Gi1/0/19): Posting EAP_REQ for 0xF0000090
Mar 29 2015 12:18:27.861 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 7(eapReq)
Mar 29 2015 12:18:27.861 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_request
Mar 29 2015 12:18:27.861 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:27.861 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_enter called
Mar 29 2015 12:18:27.861 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:27.861 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:27.861 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:27.861 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:27.861 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:27.861 EET: EAPOL Version: 0x3  type: 0x0  length: 0x006B
Mar 29 2015 12:18:27.861 EET: EAP code: 0x1  id: 0xC  length: 0x006B type: 0x19
Mar 29 2015 12:18:27.861 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:27.861 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_request_action called
Mar 29 2015 12:18:27.924 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:27.924 EET: dot1x-packet(Gi1/0/19): Queuing an EAPOL pkt on Authenticator Q
Mar 29 2015 12:18:27.924 EET: dot1x-ev:Enqueued the eapol packet to the global authenticator queue
Mar 29 2015 12:18:27.924 EET: EAPOL pak dump rx
Mar 29 2015 12:18:27.924 EET: EAPOL Version: 0x1  type: 0x0  length: 0x006B
Mar 29 2015 12:18:27.924 EET: dot1x-ev:
dot1x_auth_queue_event: Int Gi1/0/19 CODE= 2,TYPE= 25,LEN= 107

Mar 29 2015 12:18:27.924 EET: dot1x-packet(Gi1/0/19): Received an EAPOL frame
Mar 29 2015 12:18:27.924 EET: dot1x-ev(Gi1/0/19): Received pkt saddr =0050.b67c.0c14 , daddr = 0180.c200.0003, pae-ether-type = 888e.0100.006b
Mar 29 2015 12:18:27.924 EET: dot1x-packet(Gi1/0/19): Received an EAP packet
Mar 29 2015 12:18:27.924 EET: EAPOL pak dump rx
Mar 29 2015 12:18:27.924 EET: EAPOL Version: 0x1  type: 0x0  length: 0x006B
Mar 29 2015 12:18:27.924 EET: dot1x-packet(Gi1/0/19): Received an EAP packet from 0050.b67c.0c14
Mar 29 2015 12:18:27.924 EET: dot1x-sm(Gi1/0/19): Posting EAPOL_EAP for 0xF0000090
Mar 29 2015 12:18:27.924 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_request, got event 6(eapolEap)
Mar 29 2015 12:18:27.924 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_request -> auth_bend_response
Mar 29 2015 12:18:27.924 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_enter called
Mar 29 2015 12:18:27.924 EET: dot1x-ev(Gi1/0/19): dot1x_sendRespToServer: Response sent to the server from 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:27.929 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_request_response_action called
Mar 29 2015 12:18:28.044 EET: dot1x-packet(Gi1/0/19): Received an EAP Success
Mar 29 2015 12:18:28.055 EET: dot1x-sm(Gi1/0/19): Posting EAP_SUCCESS for 0xF0000090
Mar 29 2015 12:18:28.055 EET:     dot1x_auth_bend Gi1/0/19: during state auth_bend_response, got event 11(eapSuccess)
Mar 29 2015 12:18:28.055 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_response -> auth_bend_success
Mar 29 2015 12:18:28.055 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_exit called
Mar 29 2015 12:18:28.055 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_success_enter called
Mar 29 2015 12:18:28.055 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_response_success_action called
Mar 29 2015 12:18:28.055 EET:     dot1x_auth_bend Gi1/0/19: idle during state auth_bend_success
Mar 29 2015 12:18:28.055 EET: @@@ dot1x_auth_bend Gi1/0/19: auth_bend_success -> auth_bend_idle
Mar 29 2015 12:18:28.055 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_bend_idle_enter called
Mar 29 2015 12:18:28.060 EET: dot1x-sm(Gi1/0/19): Posting AUTH_SUCCESS on Client 0xF0000090
Mar 29 2015 12:18:28.060 EET:     dot1x_auth Gi1/0/19: during state auth_authenticating, got event 12(authSuccess_portValid)
Mar 29 2015 12:18:28.060 EET: @@@ dot1x_auth Gi1/0/19: auth_authenticating -> auth_authc_result
Mar 29 2015 12:18:28.060 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticating_exit called
Mar 29 2015 12:18:28.060 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authc_result_enter called
Mar 29 2015 12:18:28.060 EET: %DOT1X-5-SUCCESS: Authentication successful for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:28.060 EET: dot1x-ev(Gi1/0/19): Sending event (2) to Auth Mgr for 0050.b67c.0c14
Mar 29 2015 12:18:28.060 EET: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x' for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF

Mar 29 2015 12:18:28.065 EET: %AUTHMGR-5-VLANASSIGN: VLAN 313 assigned to Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:29.135 EET: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:29.135 EET: dot1x-ev(Gi1/0/19): Received Authz Success for the client 0xF0000090 (0050.b67c.0c14)
Mar 29 2015 12:18:29.135 EET: dot1x-redundancy: State for client  0050.b67c.0c14 successfully retrieved
Mar 29 2015 12:18:29.161 EET: dot1x-sm(Gi1/0/19): Posting AUTHZ_SUCCESS on Client 0xF0000090
Mar 29 2015 12:18:29.161 EET:     dot1x_auth Gi1/0/19: during state auth_authc_result, got event 23(authzSuccess)
Mar 29 2015 12:18:29.161 EET: @@@ dot1x_auth Gi1/0/19: auth_authc_result -> auth_authenticated
Mar 29 2015 12:18:29.161 EET: dot1x-sm(Gi1/0/19): 0xF0000090:auth_authenticated_enter called
Mar 29 2015 12:18:29.161 EET: dot1x-ev(Gi1/0/19): Sending EAPOL packet to 0050.b67c.0c14
Mar 29 2015 12:18:29.161 EET: dot1x-ev(Gi1/0/19): Role determination not required
Mar 29 2015 12:18:29.161 EET: dot1x-registry:registry:dot1x_ether_macaddr called
Mar 29 2015 12:18:29.161 EET: dot1x-ev(Gi1/0/19): Sending out EAPOL packet
Mar 29 2015 12:18:29.161 EET: EAPOL pak dump Tx
Mar 29 2015 12:18:29.161 EET: EAPOL Version: 0x3  type: 0x0  length: 0x0004
Mar 29 2015 12:18:29.161 EET: EAP code: 0x3  id: 0xC  length: 0x0004
Mar 29 2015 12:18:29.161 EET: dot1x-packet(Gi1/0/19): EAPOL packet sent to client 0xF0000090 (0050.b67c.0c14)
0
 
Craig BeckCommented:
Thanks.

In the log I can see this...

Mar 29 2015 12:18:28.060 EET: %DOT1X-5-SUCCESS: Authentication successful for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:28.060 EET: dot1x-ev(Gi1/0/19): Sending event (2) to Auth Mgr for 0050.b67c.0c14
Mar 29 2015 12:18:28.060 EET: %AUTHMGR-7-RESULT: Authentication result 'success' from 'dot1x' for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF

Mar 29 2015 12:18:28.065 EET: %AUTHMGR-5-VLANASSIGN: VLAN 313 assigned to Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:29.135 EET: %AUTHMGR-5-SUCCESS: Authorization succeeded for client (0050.b67c.0c14) on Interface Gi1/0/19 AuditSessionID 0A971407000008F5126754AF
Mar 29 2015 12:18:29.135 EET: dot1x-ev(Gi1/0/19): Received Authz Success for the client 0xF0000090 (0050.b67c.0c14)

That tells me that whatever you connected did authenticate and was dropped into VLAN313.  This was assigned by the RADIUS server.

Is VLAN313 a valid VLAN on your network, and if so, is that VLAN actually on your switch?
0
The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
Hi Craig!
To answer your question the VLAN 313 is the valid VLAN for that user. further to that this is the authentication session for that switchport:
cy1-b2-c2960-7(config-if)#do show authen session int gi 1/0/19
            Interface:  GigabitEthernet1/0/19
          MAC Address:  0050.b67c.0c14
           IP Address:  Unknown
            User-Name:  ****\****
               Status:  Authz Success
               Domain:  VOICE
       Oper host mode:  multi-domain
     Oper control dir:  both
        Authorized By:  Authentication Server
          Vlan Policy:  313
      Session timeout:  N/A
         Idle timeout:  N/A
    Common Session ID:  0A971407000008FB134054FD
      Acct Session ID:  0x00000932
               Handle:  0x270008FC

Runnable methods list:
       Method   State
       dot1x    Authc Success
       mab      Not run


So the PC definitely can see the domain and it does climb in the domain (and correct VLAN for the given user). The PC NIC though is giving me unidentified network when the authentication cycle finishes!!!
0
 
Craig BeckCommented:
Domain:  VOICE
The port is being put on the Voice VLAN.  That's interesting.  It should say DOMAIN: DATA if it's a PC as it's not passed any CDP/LLDP info to the switch.

Once the PC connects, authenticates, then receives an IP address do you get the chance to set the type of network?  Also, does the PC get a DNS suffix from DHCP?
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
Yes its very interesting because the PCs do not authenticate with any Vendor Specific Attributes that set the PC to be viewed as a voice device.
The PC is not receiving an IP address on the NIC or DNS suffix. The type of network is OSPF.

Please note that if i tag a data VLAN on the switchport the PC authenticates just fine.
0
 
Craig BeckCommented:
Please note that if i tag a data VLAN on the switchport the PC authenticates just fine.
So if I understood you correctly, if you do...

interface GigabitEthernet1/0/19
 switchport access vlan 313

Open in new window


...it works fine even with 802.1x still enabled?

The show auth sess int gi1/0/19 log you posted... is that with the PC connected directly to the switch, or via phone?
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
yeah if i tag the VLAN exactly that way the switchport authenticates the PC on the network! But that's not the implementation that i am looking for because i need the NPS server to grant access to the PC on the right VLAN based on the user's credentials.

Also another complication is that if i do tag the VLAN that way, and I connect the MITEL telephone on the switchport, the telephone authenticates just fine using MAB authentication, and then if i connect the PC to the PC port of the telephone (which is set in passthrough mode) it comes up with "unauthenticated network".
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
the auth session output is with a PC directly connected on the switchport!!
0
 
Craig BeckCommented:
Can you post the NPS log when the PC authentication passes, and also when it fails please?
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
Hi Craig,
The NPS server logs my PC as if it has connected on the network normally. According to the NPS my PC got an IP address and inherited the policy that my user was assigned to. Policy "NET_ITAdm". My computer though gets an automatic private IP address "169.254.153.76" and of course returns "unidentified network".

This is the raw detailed connection log entry:
-      System
            -      Provider
                  [ Name]       Microsoft-Windows-Security-Auditing
                  [ Guid]       {54849625-5478-4994-A5BA-3E3B0328C30D}

                  EventID      6278

                  Version      0

                  Level      0

                  Task      12552

                  Opcode      0

                  Keywords      0x8020000000000000

            -      TimeCreated
                  [ SystemTime]       2015-03-30T07:57:32.016458800Z

                  EventRecordID      37060382

                  Correlation

            -      Execution
                  [ ProcessID]       548
                  [ ThreadID]       3536

                  Channel      Security

                  Computer      cy1-dc-01.********

                  Security
      
-      EventData
            SubjectUserSid      S-1-5-21-606091427-551787605-1727263002-1338
            SubjectUserName      ********\********
            SubjectDomainName      WGCY
            FullyQualifiedSubjectUserName      ********\********
            SubjectMachineSID      S-1-0-0
            SubjectMachineName      -
            FullyQualifiedSubjectMachineName      -
            MachineInventory      -
            CalledStationID      F4-7F-35-65-39-13
            CallingStationID      00-50-B6-7C-0C-14
            NASIPv4Address      10.151.20.7
            NASIPv6Address      -
            NASIdentifier      -
            NASPortType      Ethernet
            NASPort      50119
            ClientName      cy1-b2-c2960-7
            ClientIPAddress      10.151.20.7
            ProxyPolicyName      Secure Wired Connections ********
            NetworkPolicyName      NET_ITAdm
            AuthenticationProvider      Windows
            AuthenticationServer      cy1-dc-01.********
            AuthenticationType      PEAP
            EAPType      Microsoft: Secured password (EAP-MSCHAP v2)
            AccountSessionIdentifier      -
            QuarantineState      Full Access
            ExtendedQuarantineState      -
            QuarantineSessionID      -
            QuarantineHelpURL      -
            QuarantineSystemHealthResult      -
0
 
Craig BeckCommented:
Thanks.  So can you also post a log from when you connect the PC straight to the port please?
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
This one is from when the PC connects directly to the switchport.
this log entry scenario is with the PC directly connected to the switchport and the following switchport implementation:
interface GigabitEthernet1/0/19
 switchport mode access
 switchport voice vlan 100
 no logging event link-status
 authentication control-direction in
 authentication event server dead action authorize vlan 300
 authentication event no-response action authorize vlan 1023
 authentication host-mode multi-domain
 authentication order mab dot1x
 authentication port-control auto
 authentication timer restart 900
 authentication timer reauthenticate 5400
 mab
 dot1x pae authenticator
 flowcontrol receive desired
 storm-control broadcast level 0.50 0.40
 storm-control multicast level 0.50 0.40
 spanning-tree portfast

end

Open in new window


with the authentication session:
cy1-b2-c2960-7(config-if)#do show authen session int gi 1/0/19 
             Interface:  GigabitEthernet1/0/19
           MAC Address:  0050.b67c.0c14
            IP Address:  Unknown
             User-Name:  ****\****
                Status:  Authz Success
                Domain:  VOICE
        Oper host mode:  multi-domain
      Oper control dir:  both
         Authorized By:  Authentication Server
           Vlan Policy:  313
       Session timeout:  N/A
          Idle timeout:  N/A
     Common Session ID:  0A971407000008FB134054FD
       Acct Session ID:  0x00000932
                Handle:  0x270008FC

 Runnable methods list:
        Method   State
        dot1x    Authc Success
        mab      Not run

Open in new window

0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
Where you asking for something else other than this?
0
 
Craig BeckCommented:
Yes, sorry, I'm looking for a log from NPS when the PC authenticates via the switchport instead of via the phone.
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
yes. the log I have send you has no phone daisy-chained after it. It is the PC alone directly connected on the switchport!
For some reason though the switchport puts the PC in the voice domain.
0
 
Craig BeckCommented:
Ok, it sounded like you posted a log when the PC was connected as normal (via the phone).

This doesn't make sense.  Is the PC's NIC doing VLAN tagging?

Going back to the OP...
when i connect the PC directly on the dot1x switchport it does not gain access to the domain. once i turn the implementation of the switchport to multi-host the PC authenticates with Dot1x successfully!
...that says to me that once you untag all packets going in/out of the switchport it works ok, so I'd guess that when you use multi-domain it is trunking so the NIC's traffic is dropped.
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
The NIC has no VLAN tagging settings. I got some news though. I switched my implementation to the switchport to a tagged vlan:
switchport access vlan 300

Open in new window


With this the PC authenticated on the network on the correct VLAN for the authenticated user (VLAN 313).
next when I do connect the phone in a daisy-chain format (as per my requirements), I get the following authentication session:
cy1-b2-c2960-7(config-if)#do show auth session inte gi 1/0/19
            Interface:  GigabitEthernet1/0/19
          MAC Address:  Unknown
           IP Address:  10.151.22.5
            User-Name:  UNRESPONSIVE
               Status:  Authz Success
               Domain:  DATA
       Oper host mode:  multi-host
     Oper control dir:  in
        Authorized By:  Guest Vlan
          Vlan Policy:  1023
      Session timeout:  N/A
         Idle timeout:  N/A
    Common Session ID:  0A9714070000092A178E43C9
      Acct Session ID:  0x00000967
               Handle:  0x7100092B

Runnable methods list:
       Method   State
       dot1x    Failed over
       mab      Failed over

----------------------------------------
            Interface:  GigabitEthernet1/0/19
          MAC Address:  0008.5d44.e338
           IP Address:  Unknown
            User-Name:  00085d44e338
               Status:  Authz Success
               Domain:  VOICE
       Oper host mode:  multi-domain
     Oper control dir:  in
        Authorized By:  Authentication Server
      Session timeout:  N/A
         Idle timeout:  N/A
    Common Session ID:  0A9714070000092B178E4568
      Acct Session ID:  0x00000968
               Handle:  0xAF00092C

Runnable methods list:
       Method   State
       dot1x    Failed over
       mab      Authc Success

Open in new window


The PC gets an IP address and fails for both MAB and Dot1x authentications and gets on to guest VLAN 1023. the User should have authenticated with Dot1x and get VLAN 313.
The authentication session shows that the PC was authenticated with "Oper host mode:  multi-host" instead of multi-domain.
0
 
Craig BeckCommented:
It looks like the phone isn't passing 802.1x to the PC.
0
 
Christoforos AcadjiotisSystems and Network AdministratorAuthor Commented:
The phone device, although supports 802.1x, does not understand EAP packets in order to forward to the PC. The phone device can only work 802.1x authentication with MD5 or TLS authentication.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

  • 11
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now