authenticate
1 Topic
F5OS Tenant Radius Issues
Hello All, Finished deploying new R-Series equipment to replace some i-Series. Working through some issues that I hope there is an easier solution for in regards to radius authentication on tenants/guests running on my new appliances. I cannot seem to get the tenants running on my r-series appliances to use the Mgmt IP address for radius authentication. They seem to want to use a self-ip that is within the network on the gateway for the default routing domain. For additional information the configuration on the i-series were ported over via UCS files to my r-series tenants. They're near identical besides new MGMT ips. Quick breakdown of what works for Radius R-Series Appliance (F5OS) - MGMT 1.1.1.1 <---Radius auth works using MGMT IP - Makes sense, no virtual routers - BIG-IP Tenant - MGMT 1.1.1.2 <-----Radius fails (Uses self-ip 10.10.10.10) - BIG-IP Tenant - MGMT 1.1.1.3 <-----Radius fails (Uses self-ip 23.23.23.23) - BIG-IP Tenant - MGMT 1.1.1.4 <-----Radius fails (Uses self-ip 5.5.5.5) The self IPs are all on different networks that serve different purposes on different security zones on my firewall. The solution as it stands now is allow the specific reporting self-ips to reach my radius server. I'd rather not do that if I can find a way to force to tenants to use their mgmt IP.Solved31Views0likes2Comments