Bug ID 1194381: On a windows client connected to Network Access (VPN), unplugging the LAN cable during hibernation may cause an Edge Client reconnect failure when the system resumes

Last Modified: Jun 19, 2025

Affected Product(s):
APM-Clients APM(all modules)

Known Affected Versions:
7.2.3.1, 7.2.4, 7.2.4.2, 7.2.4.3, 7.2.4.4, 7.2.4.5, 7.2.4.6, 7.2.4.7, 7.2.4.8, 7.2.5

Opened: Nov 23, 2022

Severity: 3-Major

Symptoms

In some cases, if the LAN cable is unplugged from a windows client during hibernation, Edge client may fail to reconnect when the system resumes. The Edge client will continue to display "Reconnecting".

Impact

BIG-IP Edge Client is unable to reconnect to Network Access (VPN). A restart of the BIG-IP Edge Client application is required.

Conditions

This issue occurs when followings conditions are met: 1) The Windows client system's ethernet port is connected to a physical LAN cable. 2) BIG-IP Edge Client is used to establish Network Access (VPN). 3) While BIG-IP Edge Client is connected, the Windows system is placed into a hibernation state. 4) After hibernating for at least a few minute, the Windows system is resumed.

Workaround

Add the virtual server host Address (FQDN) in the stonewall exclusion list as described in https://my.f5.com/manage/s/article/K24416258. If FQDN is not added, then use following steps: 1. The LAN cable must be unplugged from the Windows system prior to hibernation if the user does not want to continue with LAN connectivity after coming out of hibernation. 2. If step 1 is missed or skipped, and facing the Edge-Client reconnect issue after hibernation then the ethernet cable must be plugged into the system's ethernet port, and if the ethernet cable is unavailable, then restart the Edge-Client.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips