Hi Wyatt,
Have you given thought to providing us with controls that might manage how a hardware fingerprint is established? I ask because TurboFloat isn't happy with my client's somewhat uncommon hardware configuration, but I think it could be, with a small nudge.
We would like to use floating licenses across several Linux systems connected together as a computational cluster. Here's the issue: these systems do not have Ethernet interfaces. They are instead networked using InfiniBand host adapters, a type of high-performance interconnect. At runtime the TurboFloat library fails to generate a hardware fingerprint from this device because the active IP network in "/proc/net/dev" is named ib0 instead of eth0 or en0, etc.
Their network is configured with an emulation layer for IP traffic called IP-over-InfiniBand (IPoIB), so the systems should be able to communicate with the floating license server just fine. The emulated IP device also has a standard MAC address. I feel that if I could just provide TurboFloat with a fallback list of network devices to query, the whole process would probably succeed. Would something like that be possible?
Thanks
We don't have any InfiniBand hardware on hand, so we haven't developed any support for it. It seems to be a niche communications standard that modern Ethernet tends to outperform (at lower costs).
We might dedicate some resources to developing support for it if someone donated hardware to us. But we have no plans to buy InifiBand hardware (because it's so expensive and so infrequently used).