Skip to content

Configurable Internal Port Range

Choose a tag to compare

@mlhpdx mlhpdx released this 01 May 18:09
· 30 commits to master since this release

This update includes a couple changes, the big one being the ability to specify the range of ports to use for communication with backend targets. Previously SLB would defer to the OS to pick any available port. Version 2.4.0 changes that behavior by adding the command-line argument internalPortRange which is used as a pool for internal ports. The serverPortRange and internalPortRange can't overlap.

The second change is that when an inquiry is received for a known client, the response will include the assigned internal port.