Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 May 13, 2024

why EVEN TCP SOURCE PORT for remote access ?

it seems like the appliance is opening remote connections with always a even source port as shown within file : KLM-Even-Src-Port.pdf

Our network team indicated that it may raise an issue on F5 ( BIPIP equipment ) because it uses the same processor.

In case the source port is a random value ( even and odd ) then probably the transaction will be load balanced properly.

Is there any type of configuration on datapower that might explain his behavior (even source port ) ?

Idea priority High
  • Admin
    Ulas Cubuk
    Reply
    |
    Jul 4, 2024

    Thanks for raising this - in this particular case, this behavior is working as designed.

    This was enhancement to the underlying Linux kernel for better use of ephemeral ports and reduce contention between connect() and bind(). You can find the answer to your questions in the following RHEL technote: Why only even number source ports are assigned as ephemeral TCP source port? (link)

  • Guest
    Reply
    |
    May 28, 2024

    It will be interesting to link this requirement with LACP configurations