Multiple radius proxies in one hive?

  • 2
  • Question
  • Updated 5 years ago
  • Answered
Is there a way to have different radius server settings (one per Network Policy) connecting to different local Active Directory sources (one AD forrest with regional AD controllers)?
When we change the authentication settings (Radius Servers) in one Network Policy the settings will be also changed in all other network Policies located in the same hive.
Photo of DL


  • 1 Post
  • 0 Reply Likes

Posted 5 years ago

  • 2
Photo of Julian Frede

Julian Frede

  • 7 Posts
  • 5 Reply Likes
Hi, I just thought no problem. Then I tried. You are perfectly right. At least in 5.1r4 if you change one radius you change all.

Should it be that way?
Photo of Tash Hepting

Tash Hepting

  • 55 Posts
  • 29 Reply Likes

Is this because you're using the same SSID object in each of the network policies? Any changes on one SSID will be reflected across all network policies using that SSID.

If you are, you can probably solve this two ways: create unique SSID objects per network policy (yuck - don't do that), or use device classification to specify different RADIUS server IP addresses per location.

Device classification is a pretty powerful feature which allows you to easily customize certain configuration elements (like an IP address) based on tags applied to one of more devices. In this case you would redefine the IP address of the RADIUS server based on the location of the APs. The tags can be based on topology map (even if you don't use the map, just create a structure and pop the APs anywhere on the floor/building), custom defined tags (3 per device), or individual device overrides. You can also define a global default, which is what you end up with by default. Here's a screen shot of what it would look like. You get to this screen by clicking the "+" next to the IP address field instead of typing an IP directly in or using the dropdown.

Look up "IP Object/Host Name Settings" in the help for more information on this feature.