Question
How to dictate licensing communication to be prioritize on IPv4 or IPV6 addresses (to be used for communication with client) or use only one of them?
Answer
FNP_IP_ENV
This client-side environment variable determines how the client's IP address is presented to the server.
• If the variable is set to a value of 0, 4, or 6, the IP address sent to the server is resolved on the client, from the client's hostname, as follows:
• If the variable is set to 0, then the client resolves its hostname to both an IPv4 and an IPv6 address.
• If the variable is set to 4, then the client resolves its hostname only to an IPv4 address.
• If the variable is set to 6, then the client resolves its hostname only to an IPv6 address.
• If the variable is set to 1 (default value), the client-side hostname resolution is bypassed. Instead, the client's IP address is determined from the socket connection at the server, which means that a NAT-translated IP address for the client can be obtained.
FNP_IP_PRIORITY
The environment variable FNP_IP_PRIORITY decides the IP priority for hostname resolution, and can apply to the server, the client, or utilities like lmhostid. Values are:
• 4 (default): hostname resolution is attempted to IPv4 address first; if that fails, resolution to IPv6 address is attempted.
• 6: hostname resolution is attempted to IPv6 address first; if that fails, resolution to IPv4 address is attempted.
Examples of when to set to this value:
• on the machine where running lmhostid, if IPv6 address is required from lmhostid ‐internet
• on the client if node-locked IPv6 INTERNET HostID is used
• on the server if IPv6 address is used in the options file or as a server HostID.
NOTE: IPv4 and IPv6 addresses cannot be mixed on the server.
Clients send both IPv4 and IPv6 addresses in the checkout message to the server.
In some licensing models, it may be desirable for the server to operate on a NAT-translated IP address instead of the client's actual IP address—for example, if using the EXCLUDE keyword in an options file to exclude all clients originating from behind a specific firewall.
To enable such use cases, set FNP_IP_ENV=1 on the client. Setting this environment variable prevents the client resolving its own hostname to an IP address, which means the server instead obtains an IP address for the client from the socket connection.
Related Articles
Conflict between IPv4 and IPv6 lmgrd when using automatic ports: (error code: -97,121). 7Number of Views Agent communication using IPv6 IP address in beacon URL may fail with error "The URL is invalid" 1Number of Views Issues with IPv6 being preferred over IPv4 6Number of Views Troubleshooting problems with HTTP(S) communication from child to parent beacons 75Number of Views IP address not reported by Columbus Inventory Agent 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago