To support the "inactive" checkbox, which causes the Machine Tracker to also output the inactive/unused addresses of a subnet, it will always iterate over all possible addresses in the range between the entered FROM and TO-addresses.
For a typical IPv4 /24 subnet this means 2^8 iterations, which is quite fast.
For a typical IPv6 /64 subnet, on the other hand, this means 2^64 iterations. Ouch. This is our tight loop right there.
I'm working on a fix to disable the inactive-function for IPv6 addresses.
To support the "inactive" checkbox, which causes the Machine Tracker to also output the inactive/unused addresses of a subnet, it will always iterate over all possible addresses in the range between the entered FROM and TO-addresses.
For a typical IPv4 /24 subnet this means 2^8 iterations, which is quite fast.
For a typical IPv6 /64 subnet, on the other hand, this means 2^64 iterations. Ouch. This is our tight loop right there.
I'm working on a fix to disable the inactive-function for IPv6 addresses.