comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » IDL licenses thru a tunnel?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL licenses thru a tunnel? [message #34428 is a reply to message #34388] Mon, 17 March 2003 21:35 Go to previous messageGo to previous message
h_chapman is currently offline  h_chapman
Messages: 4
Registered: March 2003
Junior Member
Randall Skelton <rhskelto@atm.ox.ac.uk> wrote in message news:<Pine.LNX.4.33.0303142129250.11949-100000@moriarty.atm.ox.ac.uk>...

> Step 1:
> ^^^^^^^
>
> ssh -f -N -L 1700:idl_license_server.domain:1700 username@myserver.domain
> ssh -f -N -L 4100:idl_license_server.domain:4100 username@myserver.domain
>
>
> The second port I tunnel seems to be required for the information being
> passed back from the IDL license server. I basically sniffed packets
> while in my office to and learned that IDL was routing packets back on
> 4100 and not 1700. I have no idea how standard this is but it is
> definitely required for my setup.
>

To shed some light on the need for the second port, I found the answer
on globetrotter's faq:
http://www.globetrotter.com/flexlm/enduser_faq.htm#firewall

Apparently, the first port is for the license server proper, and the
second port is for the particular license daemon, in this case
idl_lmgr (terminology is now "vendor" in globetrotter's manuals, but
the idl license file retains "daemon"). Usually the license server
will negotiate a port for the daemon to do business on, but you can
force each daemon to be on a port you specify by adding at PORT=59000
(for example) at the end of the "DAEMON idl_lmgrd ..." line in the
license.dat.

DAEMON idl_lmgrd /usr/local/rsi/idl_5.6/bin PORT=59000

The next step is to open port 59000 (in addition to 1700) in your
firewall (if you have a firewall running on the license server), or
specify this when you tunnel. You can choose other ports for other
deamons (other licenses) in the license.dat.


> Step 2:
> ^^^^^^^
>
> Change your license.dat file to point to localhost rather than your usual
> license server.
>
> i.e.
> SERVER idl_license_server.domain 0#50##ae6#cf 1700
> becomes
> SERVER localhost 0#50##ae6#cf 1700
>
> Alternatively, instead of 'localhost'you could use your bonified machine
> hostname or 127.0.0.1. You should not need to mangle your /etc/hosts file
> as 'localhost' and 127.0.0.1 are very standard lookup names that resolve
> to your local machine.
>

Another interesting thing I learned from the globetrotter site is that
if you set the SERVER port to 27000 instead of idl's usual 1700, then
you only need @hostname instead of 1700@hostname for your
LM_LICENSE_FILE. 27000 is the default. So one of many ways of
tunnelling (this works for me) is:

export LM_LICENSE_FILE=@localhost
ssh -f -NL 27000:localhost:1700 myserver.com
ssh -f -NL 59000:localhost:59000 myserver.com
idl

type everything as written, except for myserver.com, which is the
remote machine running the license server.

Henry.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: "broken" scale in IDL plot
Next Topic: Using multiple top level bases created with GUIBuilder

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 17:43:15 PDT 2025

Total time taken to generate the page: 0.00511 seconds