Starting from tms_client 8.3.0 and Tlxconfig 4.6 (TLXOS 4.8.2, and TLXOS 4.10.0
and later) it will be possible, using a fallback MAC-address-based licensing
scheme, to license x86-based devices that were not previously licenseable due
to use of blacklisted known-non-unique hardware identifiers.

This licensing scheme will only be used when identifiers that are known to be
non-unique are detected.  TMS will warn you if this is the case.  Raspberry Pis
will never require fallback licensing, nor will the vast majority of x86-based
devices.

Fallback MAC-address-based licensing will have a significant limitation, in
order to mitigate risks of license exploits and some of the problems described
in http://help.thinlinx.com/knowledgebase.php?article=40.  The limitation is
that the licensed MAC address will be that of the network interface that
correponds to the device's primary IP address, as shown in TMS or Tlxconfig,
and if that primary interface changes after the device is licensed, the MAC
address will no longer match, and your device will revert to a 30-day trial
license.

In other words, if you substantially alter the networking arrangement of a
device using fallback licensing, e.g. change from Ethernet to WiFi or add a
VPN, then you will invalidate your license.

FYI the "primary" network interface is defined to be the interface
corresponding to the IPv4 default route with the lowest metric, if there is a
default route, or the non-loopback IPv4 route with the lowest metric otherwise.

Your primary network interface may change during the boot process, and
consequently fallback licensing may not work properly on offline networks,
because it will require access to our Internet license server to update the
license when network interface changes occur.  You may see a bogus warning
about your device being unlicensed that is only temporarily true, and you may
also see a duplicate entry in TMS because of the serial number change.