Pros and Cons for having your wireless clients (WLAN) hit RADIUS server A and B and your LAN clients hit servers C and D??

  • 1
  • Question
  • Updated 3 years ago
  • Answered
Is there a benefit either today or in the next couple of years?
Photo of intvlan1shut

intvlan1shut

  • 29 Posts
  • 1 Reply Like

Posted 3 years ago

  • 1
Photo of Mike Kouri

Mike Kouri, Official Rep

  • 1030 Posts
  • 271 Reply Likes
None that leaps to my mind. It seems like unnecessary additional complexity (how will you handle users who alternate between wired and wireless?).
(Edited)
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
You won't see high levels of resource consumption running a RADIUS server on modern hardware with typical use cases.

Unless you have exceptional needs, as Mike says, I wouldn't overcomplicate things unnecessarily.

The concern is typically how well redundancy and failover to another RADIUS server occurs, not load implications on the primary.
(Edited)
Photo of David Coleman

David Coleman, Official Rep

  • 209 Posts
  • 164 Reply Likes
I see no reason to segment wired and wireless clients via RADIUS servers.   I would be more concerned about having redundant RADIUS servers
Photo of J. Goodnough

J. Goodnough, Champ

  • 266 Posts
  • 32 Reply Likes
Agreeing with all of the above.
Photo of intvlan1shut

intvlan1shut

  • 29 Posts
  • 1 Reply Like
Thanks everyone.
Just wasn't sure if, from a security standpoint if there was any benefit now or in the foreseeable future. I appreciate all the reply's!
We've got redundant servers so we're set there. There were various reasons why we spun up the newer 2012 servers for the WiFi...I think the main reason was due to an issue with 2008 only allowing a certain # of concurrent RADIUS clients at any given time where as 2012 didn't have that limitation.