Bug ID 425377: Proxy server might cause EdgeClient to detect captive portal that does not exist

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.6.0, 11.6.1, 11.6.2, 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, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.4.1 HF9

Opened: Jul 17, 2013

Severity: 3-Major

Related Article: K17083

Symptoms

EdgeClient incorrectly detects captive portal if requests go through tunnel and then through BIG-IP-defined proxy server.

Impact

EdgeClient might detect captive portal that does not exist.

Conditions

If proxy server is enabled for Network Access, then captive portal is incorrectly detected when the following conditions are met: 1) All IP traffic is routed to tunnel (either the Force all traffic through tunnel option is enabled or split tunneling with address space such as 0.0.0.0/0.0.0.0 is used). 2) Proxy server redirects HTTP requests.

Workaround

None.

Fix Information

BIG-IP Edge Client now correctly detects captive portal if requests go through tunnel and then through BIG-IP-defined proxy server.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips