In a situation where an environment has multiple RADIUS events, the RADIUS event that is intended to be used by the connecting RADIUS client is determined by the NAS-Identifier which is sent with the request.

Some systems do not provide the option to define a NAS-Identifier attribute so the request ends up going against the RADIUS event that has no NAS-Identifier defined.

As we need to define clients under a specific RADIUS event, it would be nice if no NAS-Identifier is sent with the request, then the RADIUS event used is the one that the IP address shows up under.

by: Tim S. | over a year ago | Configuration

Comments

• this is a no brainer and is needed

  by: Jeff V. | over a year ago

• Planned for 6.3

  by: Troy D. | over a year ago

• Working great on 6.3 - thanks :-)

  by: Werner H. | over a year ago