Radius reachability problem on VOSS
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-17-2022 09:57 AM
Hi everybody,
Trying to set up a management radius connection on VOSS switch, all works fine but I'm unable to have a correct radius servers reachability.
Radius connection on CLI works well, but no dummy packets are sent to nac server (I can't see anything with tcpdump on server), so when it goes down, new connection lags because switch still try to authenticate towards server...
Any idea ?

(exemple here with web access)
Rodjeur
Trying to set up a management radius connection on VOSS switch, all works fine but I'm unable to have a correct radius servers reachability.
Radius connection on CLI works well, but no dummy packets are sent to nac server (I can't see anything with tcpdump on server), so when it goes down, new connection lags because switch still try to authenticate towards server...
Any idea ?
Rodjeur
5 REPLIES 5
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎03-21-2022 08:24 AM
Thanks for your response, I've finally got my mistake: EAPoL is disabled in my environnment. I don't need it at all, especially because I'm testing Fabric at edge deployment and NAC is not an option in my production network (too many complicated to manage with BYOD and unknown devices) and it's not possible to disable EAPoL on an auto-sense enabled port. So I must disable EAPoL globally, unless it exists an another way to achieve this.
@Ludovico Stevens, could this design evolved ? Without radius reachability for cli or web connections, in case of servers unavailability, timouts about 30 sec occur at each connection, which is not optimal...
​​​​​
@Ludovico Stevens, could this design evolved ? Without radius reachability for cli or web connections, in case of servers unavailability, timouts about 30 sec occur at each connection, which is not optimal...
​​​​​
