Bug ID 518583: Network Access on disconnect restores redundant default route after looped network roaming for Windows clients

Last Modified: Aug 19, 2026

Affected Product(s):
BIG-IP APM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 hf1, 11.5.1 hf2, 11.5.1 hf3, 11.5.1 hf4, 11.5.1 hf5, 11.5.1 hf6, 11.5.1 hf7, 11.5.1 hf8, 11.5.1 hf9, 11.5.1 hf10, 11.5.1 hf11, 11.5.2, 11.5.2 hf1, 11.5.3, 11.5.3 hf1, 11.5.3 hf2, 11.5.4, 11.5.4 hf1, 11.5.4 hf2, 11.5.4 hf3, 11.5.4 hf4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.1.0, 12.0.0

Opened: Apr 16, 2015

Severity: 3-Major

Symptoms

Windows Network Access restores redundant default route if client roaming from networks in loop e.g.: NetworkA -> NetworkB -> NetworkA.

Impact

Incorrect default route may cause routing issues on client machine if metric of interfaces connected to NetworkB is lower than metric of interfaces connected to NetworkA

Conditions

* Connect NIC to NetworkA * Connect to VPN * Roam to another wifi network SSID (NetworkB) * Roam back to the original wifi SSID in step #1 (NetworkA)

Workaround

N/A

Fix Information

Fixed issue causing redundant default route under described conditions.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips