[Thinlinc-technical] Bind HTML5 Webaccess to specific IP

Henrik Andersson henrik.andersson at cendio.com
Tue Aug 12 10:40:20 CEST 2014


Hi,

> The Server with the vmsagent and master running at has got three IP.
> Now I'm trying to bind the html5 webclient to a specific IP. But as i
> read in the docs it's just possible to change the port the client is
> listening at. I also tried to redirect the traffic at 443 tcp via
> iptables to 300. But then the html5 client is redirecting to the
> vsmagent ip:300 thus i configured a login_page = vmsagent:443.
> 

All services of ThinLinc listens on all interfaces and we have left it
to the administrator to use local firewall to lock down access for
different services on different interfaces.

I believe you have misinterpreted the use of /webaccess/login_page. It
is used in a ThinLinc cluster eg. more than one agents to get the
browser client back to the login page on the master server in the
cluster when needed. This is a bit fuzzy but if you think about
general ThinLinc login which first connects to the master and
authenticates the user and redirects the user to a session on an agent,
it becomes a bit clearer.

I don't think you can accomplish what you want on a single ThinLinc
server setup. The only way is to change /webaccess/listen_port to 443
and add a rule to open that port for the specific interface you want to
use. Which only could be realized if you don't have any other service
bound to port 443 on your ThinLinc server.


Kind Regards,

Henrik Andersson (Cendio AB)

 


More information about the Thinlinc-technical mailing list