Enabling RADIUS Agent diagnostics

Using RADIUS Agent | Web Protection Solutions |v8.2.x, v8.3.x

RADIUS Agent has built-in diagnostic capabilities, but these are not activated by default. To activate RADIUS Agent logging and debugging:

Use the Windows Services tool or /opt/Websense/WebsenseDaemonControl command to stop RADIUS Agent.

Navigate to the bin directory (C:\Program Files\Websense\Web Security\bin or /opt/Websense/bin/, by default) and open the wsradius.ini file in a text editor.

Locate the [RADIUSAgent] section.

To enable logging and debugging, change the value of DebugMode to On:

DebugMode=On

To specify the log detail level, modify the following line:

DebugLevel=<N>

N can be a value from 0-3, where 3 indicates the most detail.

Modify the LogFile line to indicate the name of the output file:

LogFile=filename.txt

By default, log output is sent to the RADIUS Agent console. If you are running the agent in console mode (see Running RADIUS Agent in console mode), you can optionally keep the default value.

Save and close the wsradius.ini file.

Start RADIUS Agent.

If remote users are not being identified and receiving correct policies as expected, the likely cause is communication problems between RADIUS Agent and your RADIUS server. Check your RADIUS Agent logs for errors to determine the cause.