Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace DataPower Gateway
Created by Guest
Created on Jul 19, 2023

Allow TCP connection when DP backside calls DP frontside over a external loadbalancer (e.g. for wrapper APIs)

We have the necessity to call another Gateway provided API from within an API (wrapper API).

For reasons of continuity those requests should have the same URL, as a client request.

We are working with external load balancer, so DNS resolves to load balancer IP --> Packets are routed out over backside interface, are routed to the loadbalancer and then back to a DP frontside interface in the loadbalancer group.

If coincidentally the same DP device gets the request, no TCP ACK is send, the packets are dropped. (See linked case for details)

We currently have a workaround with local host aliases resolving a loopback address (127.0.x.y), but this is a very static thing causing maintenance expense.

We would prefer correctly routing of packages inside DataPower, even the package has turend a round outside DP.

Idea priority Medium
  • Admin
    Ulas Cubuk
    Oct 20, 2023

    Many thanks again for submitting your idea to IBM, we truly value the time you took to do so.  Unfortunately, responding to a SYN request from an IP that is owned by another interface on the same DataPower would require massive changes at the network layer, the cost to implement the wider architectural changes which would be needed to support this are not so small. I'm sorry we are unable to progress your idea further at this time. The idea has therefore been moved to the not under consideration state.