Thank you for this, sorry, but I have to ask for additional info, this to see if I understand the feature correctly.
I was never very interested in the superclient (now aliasclient) idea, because my pi doesn't see the MAC addresses of the devices that use pihole (pi is on an isolated physical segment of my network). It looks like the approach has changed over time (MAC address dependency is gone), making it possibly useful for my network layout.
Please confirm if my interpretation is correct.
In the aliasclient table, I simply enter (example):
In the network table, I would than add the aliasclient_id (1) to all the entries related to that machine (Y50)
There are a lot of entries, because Windows 10 uses temporary IP addresses, which change every day or every restart.
I than issue the command pkill -RTMIN+3 pihole-FTL (see signals in the documentation - thanks for that)
result in the pihole-FTL log:
[2021-01-19 12:43:08.018 1145M] Received: Real-time signal 3 (37 -> 3)
[2021-01-19 12:43:08.046 1145/T1149] Imported 1 alias-client
result in the dashboard:
It's correct that I don't see the aliasclient name in the query log:
Since I see the aliasclient name in the dashboard, I assume I'm understanding things correctly, just need to write a script to add the correct alliasclient_id to the network table, whenever a new temporary IPv6 is added to the network_addresses table