What impact this command "fnsysctl killall eap_proxy" will have on the firewall ?

[martyyy]

I'm seeing the eap-proxy daemon utilizes high CPU usage. Suspecting that this may cause of the flapping on the IPSec tunnel phase 1.

# diagnose sys top-all 1 100 1
Run Time: 235 days, 16 hours and 28 minutes
4U, 0N, 10S, 83I, 0WA, 0HI, 3SI, 0ST; 7979T, 3432F
eap_proxy 1218 R 99.9 0.1 7

 the killed daemon is /bin/eap_proxy: status=0x0
 the killed daemon is /bin/eap_proxy: status=0x0
 the killed daemon is /bin/eap_proxy: status=0x0
 the killed daemon is /bin/eap_proxy: status=0x0
 the killed daemon is /bin/eap_proxy: status=0x0

My question is we only have issue with one tunnel that also flaps once or twice in an hour. Rest of the tunnels are fine. What impact this command "fnsysctl killall eap_proxy" will have on the firewall ? WIll it kill all the VPN tunnels ?

TIA. :)

[AEK]

This looks like bug:

946796

The eap_proxy daemon may keep reloading randomly due to failing to bind a port. This will cause an IKE and WiFi authentication failure.

Or this one:

923164

EAP proxy daemon may keep reloading after updating the certificate bundle.

In both cases update your FOS to 7.2.8 or if you are at 7.4 then update to the latest patch and it should fix the eap_proxy issue.

[martyyy]

Hi @AEK 

Thanks for your response.

I'm not seeing the bug ID 946796 and 923164 for FortiOS 7.2.4

https://docs.fortinet.com/document/fortigate/7.2.4/fortios-release-notes/236526/known-issues

Thank you.

[AEK · Accepted solution]

Hi @martyyy 

At least 923164 has been fixed in 7.2.6.

https://docs.fortinet.com/document/fortigate/7.2.6/fortios-release-notes/289806