To resolve this problem proceed following steps:

Delete the corrupted configuration file

You will require elevated privileges to perform this step.

Kill the process wpa_supplicant.exe

You will require elevated privileges to perform this step.

The Client service will generate the configuration file based on the template.

5.) wpa-supplicant running

A successful start of the wpa-supplicant can be verified by:

The Process Explorer or Task Manager will show for every network interface using 802.1X, a wpa-supplicant, named "wpa_supplicant.exe" as child process of "phions.exe" appearing in the Process Explorer or Task Manager

If verbose output is enabled following verbose output needs to be present in the log files:

Table 14–8wpa-supplicant running – phions.log

Item

Output

Description

 

 

 

802.1X

[009001000001]

stating that 802.1X monitoring is enabled

 

 

 

 

[009004000002]

stating the authentication method (machine, user, user with

 

 

certificate)

 

 

 

 

[009002000009]

802.1x monitor created

 

 

 

 

[009001000002]

reloading adapter list for wpa_supplicant

 

 

 

Non-ethernet adapters

[009001000003]

adapter found to be non-ethernet

 

 

 

Virtual adapters

[009001000003]

found virtual adapter …

 

 

 

Disabled adapters

[009001000003]

found disabled adapter …

 

 

 

Active adapters

[009001000004]

802.1x disabled for adapter …

 

 

 

Table 14–9wpa-supplicant running – wpa_supplicant_{adapter_uid}.log

Output

CTRL: Open pipe

CTRL: ConnectNamedPipe: connection in progress

Initializing interface '{adapter_uid}' …

14.3.7Runtime

During runtime the wpa-supplicant will re-authenticate periodically. This can be triggered either by the Client service or the switch.

192 802.1X – Technical Guideline

Page 194
Image 194
Barracuda Networks VERSION SP4 manual Runtime, To resolve this problem proceed following steps