Bug ID 521506: Network Access doesn't restore loopback route on multi-homed machine

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: May 05, 2015

Severity: 3-Major

Symptoms

Network Access on Windows doesn't restore loopback route for one adapter on multi-homed (Ethernet + Wi-Fi) machine.

Impact

Minor routing issues may occur if one special loopback is removed. To restore this route affected adapter should be disabled and enabled.

Conditions

This issue happens if: 1. Network Access was established via Ethernet 2. Ethernet cable was unplugged 3. Network Access reconnects using Wi-Fi 4. Ethernet cable is plugged in back

Workaround

None

Fix Information

Fixed issues causing improper routing table management.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips