Current ROS implementation allows DHCP-server to auth lease against RADIUS server (either internal or external) though there are limitations that make this configuration almost unusable for us:

1. if DHCP pools are configured and RADIUS tells Framed-IP-Pool attribute instead of Framed-IP-Address in Access-Response, there's no way to tell back to RADIUS which IP-address was leased to endpoint (except shell/API which runs us to race conditions very easily)

2. if DHCP-server released IP (for example by DHCP-RELEASE received from client) there's no way to tell that to RADIUS

Could those 2 capabilities implemented to ROS (for example via adding Accounting and sessions handling to DHCP-server?)

OK. I've got an answer from MT Support that said something like 'you can always check the state via API/CLI'. Whoever is that person, have you actually read the support request text?

I'm still waiting for more adequate answer from somebody more attentive. Is this such an odd request to make ROS more consistent?

Current ROS implementation allows DHCP-server to auth lease against RADIUS server (either internal or external) though there are limitations that make this configuration almost unusable for us:

1. if DHCP pools are configured and RADIUS tells Framed-IP-Pool attribute instead of Framed-IP-Address in Access-Response, there's no way to tell back to RADIUS which IP-address was leased to endpoint (except shell/API which runs us to race conditions very easily)

2. if DHCP-server released IP (for example by DHCP-RELEASE received from client) there's no way to tell that to RADIUS

Could those 2 capabilities implemented to ROS (for example via adding Accounting and sessions handling to DHCP-server?)

+1

would be very useful!

Current ROS implementation allows DHCP-server to auth lease against RADIUS server (either internal or external) though there are limitations that make this configuration almost unusable for us:

1. if DHCP pools are configured and RADIUS tells Framed-IP-Pool attribute instead of Framed-IP-Address in Access-Response, there's no way to tell back to RADIUS which IP-address was leased to endpoint (except shell/API which runs us to race conditions very easily)

2. if DHCP-server released IP (for example by DHCP-RELEASE received from client) there's no way to tell that to RADIUS

Could those 2 capabilities implemented to ROS (for example via adding Accounting and sessions handling to DHCP-server?)

+1

would be very useful!

+1
But this like COA feature request.
But:
"*) lcd - added option to change the color-scheme;"