Bug ID 573247: GRE PPTP tunnels created via the relate_client and relate_server iRules commands may fail.

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6

Fixed In:
13.0.0

Opened: Feb 11, 2016

Severity: 3-Major

Symptoms

For GRE PPTP flows, the local port and remote port in the clientflow and serverflow have changed from any (port 0) to the PPP ethertype (0x880b). This affects iRules commands related to flow creation such as relate_client and relate_server. Using port 0 with these commands will no longer match incoming GRE PPTP packets and the packets will be dropped. These drops can be seen in the no_handler_deny counter in the tmm_stat table.

Impact

All GRE PPTP packets are dropped.

Conditions

iRule that uses the relate_client or relate_server commands to create flows to handle GRE (IP protocol 47) PPTP traffic.

Workaround

The relate_client and relate_server commands in the iRule should be edited to use 34827 (0x880b) for the local and remote port.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips