20-Oct-2023 11:24 - edited 20-Oct-2023 11:42
My Windows 2016 NPS server is receiving radius requests from my F5 LB over one it's vlan self-ips rather than the mgmt interface.
Mgmt interface ip : 10.0.0.55
NPS Server ip : 10.20.0.88
When I tried to use the cli to assign it statically I get the following :
01070330:3: Static route gateway 10.0.0.1 is not directly connected via an interface.
Is there somewhere else I need to configure this static route to the NPS server to go out through it's mgmt ip of 10.0.0.55?
Solved! Go to Solution.
20-Oct-2023 11:53
this article came in handy :
https://support.f5.com/csp/article/K13284
The following CLI command fixed the issue with radius call routing. Now the NPS server is getting proper requests off the mgmt interface of the LB.
tmsh create /sys management-route lognet network 10.0.0.55/255.255.255.255 gateway 10.0.0.1
20-Oct-2023 11:53
this article came in handy :
https://support.f5.com/csp/article/K13284
The following CLI command fixed the issue with radius call routing. Now the NPS server is getting proper requests off the mgmt interface of the LB.
tmsh create /sys management-route lognet network 10.0.0.55/255.255.255.255 gateway 10.0.0.1