Bug 3003 - Support connecting to multiple servers via one IP
Summary: Support connecting to multiple servers via one IP
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VSM Agent (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2009-01-28 14:27 CET by Peter Åstrand
Modified: 2024-03-01 10:57 CET (History)
1 user (show)

See Also:
Acceptance Criteria:


Description Peter Åstrand cendio 2009-01-28 14:27:11 CET
For some ASP cases, the customer might want to expose only one single external IP, but still use a thinlinc cluster with multiple agent machines. This can be done by connecting to different TCP ports, instead of different host names. One client based solution for this is bug 1580: Assuming this mechanism supports ports, you can map different agent host names to the single external IP, but different ports. 

Being a client side solution, however, this requires a preconfigured tlclient.conf. For many ASP cases, it might be better to specify this on the server side. This could be done by extending the agent_hostname mechanism to include a port. 

The interaction with the current port setting needs to be considered, though. For example, should be agent_hostname port have higher or lower priority than the client setting?
Comment 1 Karl Mikaelsson cendio 2016-10-18 15:57:58 CEST
See also: bug 3161.
Comment 3 Pierre Ossman cendio 2022-06-07 16:05:33 CEST
Also note that the client side fix (HOST_ALIASES) only works for the native client. We have no solution for how to solve this scenario when using Web Access.

Note You need to log in before you can comment on or make changes to this bug.