Table of Contents * Previous Chapter * Next Chapter

Q2. Hostids

Q2.1 How do I get the system hostid?

This differs by hardware platform and operating system. You can always get the hostid using the lmhostid command. However, customers that don't have access to lmhostid often need to get the hostid. The following is a list of the most popular operating systems:

• HP700 (32-bit)uname -i, and prefix with a '#'
  e.g. 778DA450 or #200577134
• RS-6000/AIX (32-bit)uname -m, remove last 2 digits, then use last 8 digits
  e.g. 000276513100 --> 02765131
• SCO/Unix (String)uname -x, then prepend with ID_STRING=
  e.g. ID_STRING=SCO00354
• SGI/Irix echo `/etc/sysinfo -s` and convert to hex from decimal.
  e.g. 69064C3C or #1762020412
• SUN hostid
  e.g. 170a3472
• VMS ncp
  e.g. 0800200055327
• Windows/NT (Ethernet)lmutil lmhostid (Windows: Supports ODI, NDIS and Packet Driver Ethernet interfaces. NT: Supports `NWLink IPX/SPX' and 'NetBEUI' available from NT system CD)
  e.g. 0800200055327
• Windows/NT (32-bit volume serial number) DIR C:\ and look for `Volume Serial Number is', and remove '-'.
  e.g. DISK_SERIAL_NUM=1CA25283
• Windows/NT (dongle) lmhostid -flexid
  e.g. FLEXID=7-2850003
• Windows/NT (without using lmutil)
  e.g. winipcfg /all (Windows)
  e.g. ipconfig /all (NT)

Q2.2 On HP700 the hostid seems to be blank. Why?

Because obtaining the ethernet address (which is sometimes used as the hostid on hp700 systems) requires read and sometimes write permissions on `/dev/lan0'. To fix this,

1) log in as root 

2) type `chmod 777 /dev/lan0'

No, this is not a security hole. It is trivial to read TCP packets by simply connecting a notebook computer to the net. System administrators should assume these packets are readable. Therefore, changing permissions on /dev/lan0 is not a security problem.

We've seen postings suggesting using setuid to get around this problem. Using setuid is a serious, real security hole; setting permissions on /dev/lan0 is not.

Better yet, use the uname -i hostid. This is the default hostid produced by lmhostid.

Q2.3 At some HP sites lmhostid gives an ethernet hostid, and at others a uname -i hostid. Why?

Until v3.0 of FLEXlm (1994), FLEXlm only supported ethernet hostid on hp700. Since v3.0 FLEXlm supports both ethernet and uname -i hostids. FLEXlm can automatically determine what kind of hostid is provided and validate accordingly.

The uname -i hostid is preferred, where possible.

Q2.4 On NT, I'm getting a 0 hostid (or FFFFFFFF)--how do I fix this?

Using this type of hostid requires either the SNMP service, the NETBEUI Transport Protocol, or the NW Link (IPX/SPX) Transport Protocol to be loaded

To install the NETBEUI or NW Link Transport Protocol:

Put the NT system disk in the CDROM drive.

Select `Main'

Select `Control Panel'

Select `Network'

Select `Add'

And add the NWLink IPX SPX or NetBEUI driver.

Q2.5 What are special Hostids?

Flexlm contains a numer of "special" hostid types which apply to all platforms. These hostid types can be used on either a SERVER line or a FEATURE line, wherever a hostid is required.

• DEMO - Like ANY, but indicates a demo license.
• DISPLAY=disp - Locks the software dispaly to "disp".
• HOSTNAME=node - Locks the software to computer hostname "node".
• INTERNET=nnn.nnn.nnn.nnn - Locks the software to an Internet IP address.wildcards are allowed:
  123.123.123.*
• ANY - Locks software to any node.

Table of Contents * Previous Chapter * Next Chapter