VBR Console Ports for unused functions

[Hunv]

Hi,

we have a very restrictive environment and are allowed to open only ports that are required to pass the firewall.
We use the VBR Console from our client systems. To be able to do so, we allowed the ports that are required for the functions we use. This excludes for example all the cloud-plugin stuff. When we use the VBR Console from the client to connect to the VBR Server, it takes about 2 minutes until the console opens.

I checked if we missed some ports in the firewall and recognized that the VBR Console seems to wait for a timeout when it tries to connect to several unused plugins. This affects the following ports: 8543, 9402, 20443, 9403, 9404, 8545, 8544 and possibly 2741. This ports are for the plugins of AWS, KVM, Proxmox, etc. As mentioned: all not used and unconfigured.
I can see, that the VBR console tries to connect to each of the mentioned ports with a pause of about 20 seconds between all of them. 20 seconds is the timeout of the TCP connection.
Is this an expected behavior? It would be nice to fullfil hardening standards ("only allow what you use") while not to wait for a decade until the VBR console opens.

[Mildur]

Hi Hunv

Yes, opening these ports right now is recommended.

If you need to less ports, I suggest to have a look at our new version 13 and the new WebUI. It requires only port 443.
The WebUI currently supports vSphere and Hyper-V workloads, but will be extended with new workloads in each minor and major versions.

Best,
Fabian