API Gateway: Unable to open ports in iptables
Article ID: 186622
Updated On:
Products
CA API Gateway
API SECURITY
CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7)
CA API Gateway Enterprise Service Manager (Layer 7)
STARTER PACK-7
CA Microgateway
Issue/Introduction
When opening a new port in policy manager, for example, by creating a new WebSocket port, it does not show up on iptables.
Furthermore, all attempts to connect to the port get rejected
Environment
Release : 9.4
Component : API Gateway
Resolution
This can occur if the iptables file was manually edited. Our rules look for the L7 header in the file. If this is missing the dynamic job that runs to update the rules will not execute properly causing the port to not be opened.
To remedy this, either revert the manual edits or, if unsure of the changes, get a fresh copy of iptables from a new system and replace this on the problematic machine.
The file is located in /etc/sysconfig/iptables
To remedy this, either revert the manual edits or, if unsure of the changes, get a fresh copy of iptables from a new system and replace this on the problematic machine.
The file is located in /etc/sysconfig/iptables
Feedback
Yes
No
Powered by
