Barracuda Networks VERSION SP4 User Manual
Page 193
191 Barracuda NG Network Access Client - Administrator’s Guide
Alternatively the value in 1.1.A can be set by the Access Control Server, enforcing 802.1X
authentication. To enable the enforced use of 802.1X by the Access Control Server, following option
can be set:
•
Enter the Access Control Server trust-zone configuration using the Barracuda
NG Admin administration tool
•
Open the rule to enable the use of 802.1X authentication and select the view
Policy Assignments
•
Set the option
Use 802.1X Authentication
to
Yes
or
No
as desired
4.) wpa-supplicant configuration
In order for the "Client" service to run the wpa-supplicant, the wpa-supplicant requires a valid
configuration file for every network interface a supplicant will operate on. These configuration files are
located in the folder {install_directory}\wpa and generated by the Client service from a
template configuration automatically.
If the configuration file for the network interface used is corrupted, following behavior will occur:
•
The wpa-supplicant exe will terminate almost immediately and will not appear
in the Process Explorer or Task Manager
•
If verbose output is enabled:
wpa_supplicant_{adapter_uid}.log:
Line X: Invalid configuration file …
This value can also be changed within the
Advanced Settings
of the Barracuda NG Access Monitor,
IEEE 802.1X
Authentication
parameter
.
Table 14–7
Key {adapter_uid}
Item
Description
Path
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\phionuio\Parameters\Adapters\
Key
{adapter_uid}
Value
Enables or disables 8021X authentication for the adapter with the specified adapter_uid (Default=0)
• 0 - disabled
• 1 - enabled
Changes of this value take effect immediately.
This option may also be changed on the property page of the
Barracuda Networks Personal Access Client
within
the network interface's properties dialog by changing the
802.1X Authentication
option.
If an existing instance of a WPA supplicant is already running for the desired network interface while the service start
is executed on the client, then the supplicant will be terminated followed by starting a new instance.