[Thinlinc-technical] Ang: different ethernet interfaces

[Karl Mikaelsson]

Hi Johan,

/vsmagent/agent_hostname is the name vsmserver tells the client to
connect to, so this should be a name or IP that all your clients can
reach your agent on, no matter from where they connect.

If you want to limit vsmserver/vsmagent to listen to a single
hostname/IP address instead of any, you can configure the
/vsmserver/listen_hostname and /vsmagent/listen_hostname configuration
parameters. I'm afraid they are undocumented, so if things break you get
to keep all the pieces. :-)

Disallowing access to ThinLinc ports from other network interfaces could
also be implemented using a local firewall.

Regards,
Karl

Johan Kragsterman <johan.kragsterman at capvert.se> writes:
> Hej!
>
> I continue with my own questions from last mail:
>
>
> I found this in the /opt/thinlinc/etc/conf.d/vsmagent.hconf:
>
> # Public hostname; the hostname that clients are redirected to. If not
> # defined, the agent will use the computer's IP address.
> agent_hostname=
>
> Is that a good place to start with? Can I also use ip adress there, instead of
> a hostname?
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
>
>
> -----thinlinc-technical-bounces at lists.cendio.se skrev: -----
> Till: thinlinc-technical at lists.cendio.se
> Från: Johan Kragsterman
> Sänt av: thinlinc-technical-bounces at lists.cendio.se
> Datum: 2014-04-04 10:36
> Ärende: [Thinlinc-technical] different ethernet interfaces
>
>
> Hi!
>
>  Got a small test setup here, where the TL server/agent are on the same server,
> which is a KVM VM on an Illumos/OmniOS physical host.
>
>  The KVM VM is running edubuntu 13.10, and I use a combination of TL and LTSP
> (LInux Terminal Server), which means I boot thin diskless pxe clients on local
> network, and use TL clients to access from remote.
>
>  The edubuntu VM has three ethernet if, eth0 which is wan, eth1 which is the
> LTSP thin client network, and eth2, which I want TL to use. This is for
> security reasons, this if is the only one that I will allow connections from
> outside. This is also a physically isolated network, that goes directly to a
> port in the FW.
>
>  So, can anyone give me some advices here, where in the config files would I
> set this, and how would I set it? I can use an internal dns to give the ip a
> hostname, if that's a good idea.
>  The current hostname of the VM is now ltsp.hemma.home, on the eth0, I could
> perhaps use something like ltsp.tl.hemma.home on the eth2.
>
>  I'm not that very good at Linux routing, and I'm not sure if I need to alter
> some routing tables...? Would TL answer requests on the same interface that the
> request came from?
>
>  As you see, I would need, and would appreciate, some advices here...
>
>
>
> Best regards from/Med vänliga hälsningar från
>
> Johan Kragsterman
>
> Capvert
> _______________________________________________
> Thinlinc-technical mailing list
> Thinlinc-technical at lists.cendio.se
> Manage your subscription:
> http://lists.cendio.se/mailman/listinfo/thinlinc-technical

-- 
Karl Mikaelsson     derfian at cendio.se
System Developer    +46 (0)13-290863
Cendio AB           http://www.cendio.com/