Bug ID 564246: VPN cannot be used in some cases when IP filtering engine is enabled

Last Modified: May 01, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.3.0, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Opened: Dec 21, 2015
Severity: 3-Major

Symptoms

NA connects and disconnects within 30 seconds in some cases if IP filtering engine is enabled in Network Access configuration

Impact

User cannot establish VPN

Conditions

-IP filtering engine is enabled in Network Access configuration - Network Access virtual server connections are redirected to another internal virtual server in BIG-IP connfiguration

Workaround

Do not redirect Virtual server connection or disable IP filtering engine. There are a couple of other workarounds: 1. Have the same port number for both the virtual servers. 2. If the port numbers need to be different for the 2 virtual servers, insert variable assignment agent which assigns value of client facing port (443 in this case) to variable session.server.network.port. Use custom variable and Text selections of agent. example: apm policy agent variable-assign /Common/na_act_variable_assign_ag { variables { { expression "return {443}" varname session.server.network.port } } }

Fix Information

None

Behavior Change