Bug ID 973417: Stonewall service does not recognize local network on startup

Last Modified: Apr 28, 2025

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

Known Affected Versions:
7.1.8, 7.1.8.1, 7.1.8.2, 7.1.8.3, 7.1.8.4, 7.1.8.5, 7.1.9, 7.1.9.7, 7.1.9.8, 7.1.9.9, 7.2.1

Fixed In:
7.2.2, 7.2.1.1

Opened: Dec 12, 2020

Severity: 2-Critical

Symptoms

On Microsoft Windows devices, the Stonewall service does not recognize the local network on startup, as the Network Location Awareness (NLA) is not activated on the first run and the Firewall blocks the internet traffic.

Impact

Windows users that have the Always Connected client installed cannot access the network.

Conditions

1. Configure a DNS suffix and Always Connected client with Disconnected VPN option as Allow-In-LAN. 2. Install Edge Client on Windows 10, and set the DNS suffix on the network adapter as the one in the configuration (so that NLA will detect local network). 3. Reboot the machine.

Workaround

None.

Fix Information

This issue is fixed, and now NLA detects the local network successfully.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips