Related Articles

14120 - Audit log message for pool node changes made via REST API do not include the IP of the node that was changed

KB44772 - SNMP Queries traffic is sent out only from the internal/management port

SA44790 - HTTP Request Smuggling vulnerability with Virtual Traffic Manager (vTM)

5551 - Is HTTP Health Monitoring for a vTM Pool Node with Windows Integrated Authentication supported?

KB44748 - Backend node can fail with SSL-passthrough virtual server when the node rejects SSL handshake

KB25571 - Syslog traffic is sent out only from the internal/management port of the leader node in a cluster

SA43681 - 2016-11: CSRF vulnerability with Brocade Virtual Traffic Manager (vTM) (CVE-2016-8201)

KB44687 - Traffic to external server fails with "Connect failure - Network is unreachable" messages seen in logs intermittently when pool.use Traffic Script function is used

KB45128 - PSAM Traffic flow and learning about TDI and WFP driver

KB44839 - How to configure multiple remote syslog servers for sending syslog formatted request logs from a virtual server

< Back to search results

Article

KB44964 - iptables rule for sending Traffic to Pool Node from Traffic IP (TIP)

« Go Back

Information

Last Modified Date	1/11/2022 5:09 PM

Synopsis

Once the TIP (Traffic IP) receives the inbound packet, this packet is sent to the Pool node using the Interface IP
However, sometimes you may want to send the Traffic to Pool Node from the TIP itself (based on the app design etc.)
This requirement is filed internally as : VTM-29970

Problem or Goal

Cause

Solution

The workaround is to run an iptables command.

iptables -t nat -I POSTROUTING -d <destination IP> -p tcp --dport 443 -j SNAT --to <TIP>

Example:
iptables -t nat -I POSTROUTING -d 10.10.10.2 -p tcp --dport 443 -j SNAT --to 10.10.10.1

Related Links

Attachment 1

Created By	Carlos Juan