Business CommunityAll Threads802.1x authentication fails after client reboot
All Threads

802.1x authentication fails after client reboot

802.1x authentication fails after client reboot

802.1x authentication fails after client reboot
802.1x authentication fails after client reboot
3 weeks ago - last edited 3 weeks ago
Tags: #VLAN & Multi-Networks #802.1x
Model: TL-SG3428X-M2  
Hardware Version: V1
Firmware Version: 1.20.26

Hello,
 

I have configured 802.1x authentication on my switches.

 

First the 802.1x authentication is successful.

 

Then the client reboots. During the reboot there is a network disconnect.

 

Then 802.1x authentication fails because the client sends accounting request for re-auth but the switch expects a 802.1x auth request.

 

My configuration details:

One of the clients is an Apple MacMini.

 

In the OC300 controller Site -> Network config -> 802.1x -> Switch 802.1x set

Authentication Protocol: EAP
Authentication Type: MAC-Based
VLAN Assignment: Enabled
Guest VLAN:  guest

 

On the Switch configure the port with "802.1x" or "both" enabled.

  0      
0
#1
Options
3 Reply
Re:802.1x authentication fails after client reboot
3 weeks ago

Hi  @relvy 
Thanks for posting here.


As a test, please try configuring the port as 802.1X only instead of Both, and if possible use Port-Based Authentication rather than MAC-Based Authentication for the Mac Mini.

Also check whether the authenticated session remains present on the switch after the reboot. If the session is not removed, the switch may still regard the endpoint as already authorized, causing the subsequent 802.1X exchange to fail.
 

Click Here to Get the Latest Omada SDN Controller Releases Get the Latest Firmware Releases for Omada Switches Here Get the Latest Firmware Releases for Omada Routers Here Experience the Latest Omada EAP Firmware
  0  
0
#2
Options
Re:802.1x authentication fails after client reboot
2 weeks ago

  @Nathan-TP 

> As a test, please try configuring the port as 802.1X only instead of Both, and if possible use Port-Based Authentication rather than MAC-Based Authentication for the Mac Mini.

All variations have the same result.

> Also check whether the authenticated session remains present on the switch after the reboot.
If the session is not removed, the switch may still regard the endpoint as already authorized, causing the subsequent 802.1X exchange to fail.

The session switches to status "pending". Then it gets the guest vlan assigned and remains there.

  0  
0
#3
Options
Re:802.1x authentication fails after client reboot
2 weeks ago

  @relvy 

Hi,

Thank you very much for providing the relevant information.

To better assist you, we have created a support ticket via your registered email address to gather more information. Please check your inbox for further details.

 

Click Here to Get the Latest Omada SDN Controller Releases Get the Latest Firmware Releases for Omada Switches Here Get the Latest Firmware Releases for Omada Routers Here Experience the Latest Omada EAP Firmware
  0  
0
#4
Options

Information

Helpful: 0

Views: 282

Replies: 3

Tags

VLAN & Multi-Networks
802.1x