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 Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Jun 20, 2023

Force outbound traffic on secondary IP address for interface

When you talk about outgoing traffic, Datapowers (as UNIX Systems) is only able to send through primary IP address of the interface. It could be useful (as MQ is able to do for CHANNELS with LOCLADDR parameter) to be able to force outgoing traffic on any secondary IP address defined in this interface.

Imagine the case, where a customer is using LACP interface over 3 DAC 10Gb cables (eth20-21-22). He has setup 4 IPs for LACP (1prim-3sec), one for each 4 domains. And he has strict firewall policies or IP filtering rules, he only has the choice to send outbound traffic on the primary IP. So he is forced to whitelist the same IP for all environments even if it breaks it's security logic.

Idea priority Medium
  • Guest
    Sep 20, 2023

    Hello, yes ! your understanding of my case is correct. So to answer your question : what I imagined was to have a configurable IP in the output interface for each "service (WSG,MPG, etc...)". Really like a the concept of channel in IBM MQ.

    I imagine a new feature in each service when you can specify your LOCLADDR for outgoing traffic.

    The oubound interface is chosen by the routing rules table like it's currently the case

    And the IP within this previous interface is chosen by customer with the LOCLADDR parameter (new feature), with default value as Primary.

    Is it clearer for you ?


  • Admin
    Ulas Cubuk
    Aug 30, 2023

    Thanks for raising this request. We agree that it would be useful to be able to bind the outgoing traffic on a secondary IP address including secondary address on an LACP interface.

    For the awareness of all the readers, it is already possible to configure a Front Side Protocol Handler to bind to a specific address, therefore it is possible to use one interface for input and a different interface for output.

    Therefore, based on our understanding of your use case, the enhancement is to be able select a address for outbound flows. If that is correct could you please clarify the following points;

    Is the request to have a different output interface configurable per-domain on each domain object, or per-tenant? Or is the request to have every url-open be configurable for which interface it should go out on?