The work around we were able to leverage was instead of using the NAS-IP-Address in the Radius policy set we used the Device-Access-IP-address which is still part of the Access-Request packet. We left the NAS-IP-Add and used the OR statement. Once the bug is fixed we will revert back to using the NAS-IP only if recommended. We are using the ver. 7.7 of the FMC.
