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 Under review
Workspace Aspera Ideas
Created by Guest
Created on Nov 27, 2023

Faspex 5 - Add configuration option to change IP address range of Docker network.

When setting up Faspex 5, docker creates a default virtual network, at 172.17.0.0/16.
The 'fapexctl setup' program then creates a second virtual network, at 172.18.0.0/16.

This means that the server cannot respond to external requests for the Faspex web interface, for devices in these IP ranges.

This can be fixed, by creating the file '/etc/docker/daemon.json' and restarting the docker service, before running 'faspexctl setup':

{
  "default-address-pools":
  [
    {"base":"172.71.0.0/24","size":24}
  ],
  "bridge": "none"
}

In the above example, "bridge": "none" removes the default docker network 'docker0', as it is not being used.
"default-address-pools": [ {"base":"172.71.0.0/24","size":24} ] sets the default docker network range to 172.71.0.0/24.

It would be helpful to include two options, in '/opt/aspera/faspex/conf/docker/faspex5_containers.env', to specify the address and size of the Faspex virtual network, and (less importantly) to specify whether to disable the default docker network.

Idea priority Low