GuestForgot to mention, this is running on Linux
License checks failing due to temporary non-availability of network interface
GuestHi,
We're running into a problem with TurboActivate when used on a device with multiple network interfaces:
During certain periods (eg. the boot process and airplane mode), the main network device is not available, and the OS temporarily sets up a dummy network device.It seems that if a license check occurs during those periods (eg during the boot process to see if a service should be allowed to run) the validation fails, presumably because it the previous MAC address is temporarily not detectable and a new one is present, making it appear that the software is running on a different hardware device.
Is there any kind of API function that can address this? An instruction to always use a particular network interface, or to make it accept any of the 3 possible ones which might be available, or to ignore network device inconsistencies in the hardware check?
First of all, before you do anything else, make sure you're using the latest version of TurboActivate. Currently version 3.4.3. We've fixed a number of bugs in this area (hardware fingerprinting). So depending on the version you're currently using we've probably already fixed this bug.
and the OS temporarily sets up a dummy network device.
If you're using the current version of TurboActivate and you're still getting his behavior, then the fault is in the operating system. That is, instead of creating a new "dummy" network device it should disable the existing real network device. Same end result (no internet) except things actually work correctly (TA doesn't see the computer as different).
Also, I've never seen this "dummy network device" behavior before. Is this real behavior by a real operating system, or is this some piece of software that's doing this instead of using proper behavior (i.e. disabling real network devices).
GuestSo just to clarify - TurboActivate *should* be able to handle a situation where it appears that the network device is changing?
No, TurboActivate handles the case where the network devices are unchanged, but may or may not be disabled. It, however, does not handle the case where fake network devices are added.
In fact, I've never even seen a linux distro where fake network devices are added for no reason. Seriously, disabling real network devices would accomplish the same goal (stopping internet access) without breaking real application.