Thanks for getting back to me. We want to reduce the timers to be less than 60 seconds so devices that use MAB for auth are able to make a DHCP request which is forwarded to the DHCP server without being blocked for authentication purposes. Obviously the timers are set that the transmit is 5 seconds so I would have thought that after five seconds it would reattempt to auth with the same mechanism or it would begin trying the secondary mechanism.
Unfortunately, this is not the case and the switch waits for 60 seconds before accepting that the device is not an 802.1x supplicant and then moving over to MAB.
Is there any way we can force the switch to accept that after 5 seconds that the devices are not an 802.1x compliant supplicant and then performing MAB?
DELL-Josh Cr
Moderator
•
9.5K Posts
0
December 18th, 2019 07:00
Hi,
Yes that should help or increase the timeout to longer than 60 seconds.
TalanWestby
1 Rookie
•
13 Posts
0
December 18th, 2019 08:00
Hi Josh,
Thanks for getting back to me. We want to reduce the timers to be less than 60 seconds so devices that use MAB for auth are able to make a DHCP request which is forwarded to the DHCP server without being blocked for authentication purposes. Obviously the timers are set that the transmit is 5 seconds so I would have thought that after five seconds it would reattempt to auth with the same mechanism or it would begin trying the secondary mechanism.
Unfortunately, this is not the case and the switch waits for 60 seconds before accepting that the device is not an 802.1x supplicant and then moving over to MAB.
Is there any way we can force the switch to accept that after 5 seconds that the devices are not an 802.1x compliant supplicant and then performing MAB?
Thanks,
Talan